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

URGENT - PTAL.
Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the M61 branch #3163 ASAP to have enough baking time in Beta before Stable promotion. Thank you!

Know that this issue shouldn't block the release?  Remove the ReleaseBlock-Stable label.

Lowering priority, as this requires the --wasm-lazy-compilation flag.
Also, no security implications.

ClusterFuzz has detected this issue as fixed in range 48037:48038.

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  Builtins::kWasmCompileLazy == code->builtin_index() in module-compiler.cc
  v8::internal::wasm::InstanceBuilder::LoadTableSegments
  v8::internal::wasm::InstanceBuilder::Build
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=45772:45773
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48037:48038

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

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

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