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

Another asm-wasm issue.

ClusterFuzz has detected this issue as fixed in range 424375:424402.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4799876569497600

Fuzzer: afl_v8_wasm_code_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x625000015bf0
Crash State:
  v8::internal::wasm::ThreadImpl::DoBreak
  v8::internal::wasm::ThreadImpl::Execute
  v8::internal::wasm::ThreadImpl::Run
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=421457:421501
Fixed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=424375:424402

Minimized Testcase (0.02 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97HDduL5peUy1U0XXOHyAFYpXywErEJX9m1E_Tjor5RwC-UVYzwGlBHtrSr09-x_kRuswUsNi3E2Kpa9cHarW2blvL87DT_Cf348aaFzAR_PExMuNn67zjCjJDIYy83MsLCKBliGd7PqxHq5cXiw9kmY6GTCQ?testcase_id=4799876569497600

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 is verified as fixed, closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Any idea what fixed this in M56, so we can merge it to M55?

WASM is not active in M55 so no need to merge.

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