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

Assigning to V8 sheriff.

ClusterFuzz has detected this issue as fixed in range 487822:487826.

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

Fuzzer: arrayfuzz
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Unknown exception
Crash Address: 0x00000000
Crash State:
  RaiseException
  _callnewh
  v8::internal::BodyDescriptorApply<v8::internal::CallIterateBody,void,v8::interna
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=487540:487674
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=487822:487826

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


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 5240508418097152 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