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

Assigning to V8 sheriff for triage. If it does not have security implications, please change to Type-Bug and remove Restrict-View-SecurityTeam

https://chromium-review.googlesource.com/c/548635

This requires the --wasm-lazy-compilation commend line flag. Hence no security implications.

ClusterFuzz has detected this issue as fixed in range 46217:46218.

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  mem_size == 0 implies mem_start == nullptr in wasm-module.cc
  v8::internal::wasm::LazyCompilationOrchestrator::CompileFunction
  v8::internal::wasm::LazyCompilationOrchestrator::CompileLazy
  
Sanitizer: address (ASAN)

Regressed: V8: 44043:44044
Fixed: V8: 46217:46218

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.