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

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

Crashes reliably, but at vastly different locations in the code. Regression range inconclusive. Seems to be tied to async compilation.

A friendly reminder that M59 Beta  launch is coming soon! Your bug is labelled as Release Block Beta. All fixes need to be merged into the release branch (3071) latest by tomorrow, 04/26 4:00 PM PT in order to make into the desktop Beta final build cut. Thank you!

This issue only happens on d8, not with chrome. I remove the ReleaseBlock-Beta label therefore.

ClusterFuzz has detected this issue as fixed in range 470142:470314.

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

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Use-after-poison READ 4
Crash Address: 0x0dd75934
Crash State:
  v8::internal::wasm::WasmFullDecoder::InitSsaEnv
  v8::internal::wasm::WasmFullDecoder::Decode
  v8::internal::wasm::BuildTFGraph
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=460544:464119
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=470142:470314

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


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.

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