Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically adding ccs based on suspected regression changelists:

Add more fuzzers for Optimizer. (#1788) by dj2@everburning.com - https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/de9496e9f1b9d74c117fb4c4552ef0f5d74b8cbd

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

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

piman@, you're in the OWNERS file of third_party/SPIRV-Tools/.
Could you help triage this bug?  Please feel free to reassign.

->dsinclair who rolled in the fuzzer.

Removing RBS as this is not shipped in Chromium at the moment.

ClusterFuzz has detected this issue as fixed in range 581965:581976.

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

Fuzzer: afl_spvtools_opt_size_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x60b0000029c0
Crash State:
  spvtools::opt::Instruction::NumOperands
  spvtools::opt::analysis::DefUseManager::WhileEachUse
  spvtools::opt::analysis::DefUseManager::ForEachUse
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=580304:580305
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=581965:581976

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

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 4917208481005568 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