This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hi Brad,

Can you help get this security bug assigned to an appropriate person?
SEGV caused by READ memory address when creating a new WasmInstance*.

Thanks!

ClusterFuzz has detected this issue as fixed in range 42075:42076.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4685519603892224

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_ignition_v8_arm_dbg
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0xd9d0001c
Crash State:
  v8::internal::FixedArray::set
  v8::internal::WasmInstanceWrapper::New
  v8::internal::WasmInstanceObject::New
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: V8: r41916:41917
Fixed: V8: r42075:42076

Minimized Testcase (1.21 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96DNvLW2ybMadax5MSq-3wtieDDjAGuXF0hgxDV7dk4KETUQcjutQGsDBOdjT9jZYyotD_HAnLkwASGi9GWKLdK-I4UfPm369hSOTNwxzPIVZehICrSfAjykFttB2apG7a5DBvD9t5WICJihA9_kS5ig9Mb5w?testcase_id=4685519603892224

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.

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

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

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