ClusterFuzz has detected this issue as fixed in range 36575:36576.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x7f68c7e00038
Crash State:
  v8::internal::HandleBase::IsDereferenceAllowed
  void v8::internal::LookupIterator::Start<false>
  v8::internal::LookupIterator::LookupIterator
  
Recommended Security Severity: Medium

Regressed: V8: r36566:36567
Fixed: V8: r36575:36576

Minimized Testcase (12.90 Kb): https://cluster-fuzz.appspot.com/download/AMIfv951yBgzWPxsFy3Ob5JZKNIsByAb1nPVd7-mwMQJwXBAVukuvQ5KziBhk1mUkeAcbvTELwWweYfotitZpd4oPqfx1ZuaYYftIibdy0B3KFvZcKyaDwZh-_NKTulx5n75DhqDvgxtGNqCpJg8l5lf3hm_Y71fjg

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.

Crash within Wasm.instantiateModuleFromAsm. Seems to be flaky and regression range is inconclusive. Haven't tried reproducing locally yet. Let me know if you need help with reproducing this.

bradnelson@, have you had a chance to look at this?

I believe this is the same root cause.

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