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

Fuzzer looks recently added

https://chromium.googlesource.com/chromium/src/+/2d3ea7e52f846a0beec94fbd0027e15a4970c562

ClusterFuzz has detected this issue as fixed in range 512605:512640.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  sw::RegisterArray<16, false>::RegisterArray
  sw::VertexRoutine::VertexRoutine
  sw::VertexProgram::VertexProgram
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=512324:512353
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=512605:512640

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.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 6537503661359104 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