Looks like an async compilation failure. The bytes in the CodeDesc seem to be invalid.

Andreas, do you want to take a look?

Already fixed.

ClusterFuzz has detected this issue as fixed in range 481147:481178.

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

Fuzzer: libFuzzer_v8_wasm_async_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x7f410baddeee
Crash State:
  v8::internal::Code::flags
  v8::internal::Code::kind
  IsAtWasmDirectCallTarget
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=480794:480851
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=481147:481178

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


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.

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