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

Duping to 725929. The crash stack looks different but the suspect CL is still in the regression range, and it is one of many UaFs related to Collections popping up today.

ClusterFuzz has detected this issue as fixed in range 474847:474872.

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

Fuzzer: inferno_webbot
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x27113968
Crash State:
  blink::NodeListsNodeData::AddCache<blink::HTMLCollection>
  blink::Document::forms
  blink::WebDocument::Forms
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=474215:474241
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=474847:474872

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


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.

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