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

Major regressions from https://chromium-review.googlesource.com/c/chromium/src/+/1102690, reverting.

ClusterFuzz has detected this issue as fixed in range 567939:567940.

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

Fuzzer: marty_html_twiddler
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x1270324166e8
Crash State:
  blink::LayoutObject::IsDescendantOf
  blink::MakeCounterNodeIfNeeded
  blink::FindPlaceForCounter
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=567880:567882
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=567939:567940

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

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