ClusterFuzz has detected this issue as fixed in range 481513:481531.

Detailed report: https://clusterfuzz.com/testcase?key=6158811584004096

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x06dde8372b60
Crash State:
  Bad-cast to gl::Surface from egl::PBufferSurface
  es2::Context::makeCurrent
  egl::MakeCurrent
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=481503:481513
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=481513:481531

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6158811584004096


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6158811584004096 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

It got "fixed" by a DEPS roll revert, which was done for a different reason (Issue 735920). The change that caused this will land again, but it's a benign issue because UBSan doesn't seem to know that egl::PBufferSurface is derived from gl::Surface because it was created in a different library. The compiler knows it's a safe upcast though, so I think this is essentially a UBSan issue.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot