Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/581fd6679b8b6778509a531501b03bd7497f6653 ([wasm] enable --wasm-trap-handler by default).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

The problem is that lazily compiled wasm functions don't have their trap handler information registered. I'm working on a fix now.

Fix is out for review: https://crrev.com/c/1020361

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

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/94139bc6ac2a79d2bd384d39fd6e440e743b18a9

commit 94139bc6ac2a79d2bd384d39fd6e440e743b18a9
Author: Eric Holk <eholk@chromium.org>
Date: Mon Apr 23 18:30:24 2018

[wasm] Register trap handler data for lazily compiled functions

Bug:  chromium:834693 ,  chromium:834955 
Change-Id: I243521f45c2b7e2457a37d34ab3629670d8fa39b
Reviewed-on: https://chromium-review.googlesource.com/1020361
Commit-Queue: Eric Holk <eholk@chromium.org>
Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#52744}
[modify] https://crrev.com/94139bc6ac2a79d2bd384d39fd6e440e743b18a9/src/runtime/runtime-wasm.cc
[modify] https://crrev.com/94139bc6ac2a79d2bd384d39fd6e440e743b18a9/src/wasm/module-compiler.cc
[modify] https://crrev.com/94139bc6ac2a79d2bd384d39fd6e440e743b18a9/src/wasm/wasm-code-manager.cc
[modify] https://crrev.com/94139bc6ac2a79d2bd384d39fd6e440e743b18a9/src/wasm/wasm-code-manager.h
[add] https://crrev.com/94139bc6ac2a79d2bd384d39fd6e440e743b18a9/test/mjsunit/regress/wasm/regress-834693.js

ClusterFuzz testcase 5185473778286592 is verified as fixed, so closing issue as verified.

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

ClusterFuzz has detected this issue as fixed in range 52743:52744.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: UNKNOWN WRITE
Crash Address: 0x7f2507f8c013
Crash State:
  Call
  v8::internal::Invoke
  v8::internal::CallInternal
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=52626:52627
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=52743:52744

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

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.

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