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

I am taking this. Looks related to 735973.
Lowering priority, as this requires --wasm-interpret-all. Also, no security implications.

ClusterFuzz has detected this issue as fixed in range 47909:47910.

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  Code::WASM_TO_JS_FUNCTION == js_wrapper->kind() in wasm-interpreter.cc
  CallExternalJSFunction
  v8::internal::wasm::ThreadImpl::CallCodeObject
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=47230:47231
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=47909:47910

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

See https://github.com/google/clusterfuzz-tools 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 5183174782222336 is verified as fixed, so closing issue as verified.

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