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

If this is incorrect, please apply the Test-Predator-Wrong-Components 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

clemensh@ Could you take a look at this, or help find an owner? Clusterfuzz indicates it may be caused by changes in crrev.com/822476/ or related CLs.

ClusterFuzz has detected this issue as fixed in range 525188:525196.

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

Fuzzer: libFuzzer_v8_wasm_async_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  v8::internal::wasm::CallIndirectOperand<
  v8::internal::wasm::WasmFullDecoder<
  v8::internal::wasm::WasmFullDecoder<
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=524044:524066
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=525188:525196

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

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.

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