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

Guessing https://chromium.googlesource.com/chromium/src/+/f88b1b47594ebba08774469a5f236055104c0381 based on regression range.  yoichio, could you take a quick look and eitehr confirm or rule-out your CL?

ClusterFuzz has detected this issue as fixed in range 492570:492580.

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

Fuzzer: marty_html_twiddler
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x0800a680
Crash State:
  blink::LayoutObject::ChildAt
  blink::SelectionPaintRange::Iterator::Iterator
  blink::CollectInvalidationSet
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=489271:489278
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=492570:492580

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


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.

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