This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

This is a different warning for an old problem, not a security bug. Might be due to a bug in UBSAN itself. Going to reprioritize accordingly.

If there is a UBSan bug, I'd be glad to help either suppress it or fix on LLVM side. Do you have more information?

ClusterFuzz has detected this issue as fixed in range 509878:509903.

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

Fuzzer: libFuzzer_gpu_angle_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Incorrect-function-pointer-type
Crash Address: 
Crash State:
  egl::Display::initialize
  egl::Display::initialize
  egl::Initialize
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=500968:501035
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=509878:509903

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 5507158807674880 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the 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