Marking the issue as Won't Fix as there is not stack trace or enough stack information to triage further.
Thank You.

ClusterFuzz testcase 6411399814447104 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 503351:503380.

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

Fuzzer: libFuzzer_v8_wasm_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  NULL
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=500422:500485
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=503351:503380

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

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.