This is a use in wasm::AsyncCompileJob on a worker thread after the Isolate has been torn down by the main thread. Regression range contains almost exclusively CLs related to WebAssembly, they might however just flush out the problem.

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

ClusterFuzz has detected this issue as fixed in range 479356:479374.

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

Fuzzer: inferno_js_fuzzer
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x0b601634
Crash State:
  v8::internal::wasm::AsyncCompileJob::DecodeModule::Run
  v8::platform::WorkerThread::Run
  v8::base::ThreadEntry
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=470050:470100
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=479356:479374

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


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

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

Was probably fixed by https://chromium-review.googlesource.com/532993.

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