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

Lowering priority, as this requires the --wasm-interpret-all flag.
Also, no security implications.

ClusterFuzz has detected this issue as fixed in range 493241:493282.

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  deopt_data->get(1)->ToInt32(&index) in wasm-interpreter.cc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=489609:489673
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=493241:493282

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

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

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