Related to https://codereview.chromium.org/2840613006 /  issue 713671  ?

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

eae, this is the CHECK you added in https://codereview.chromium.org/2840613006. Removing security labels since the CHECK should remove any security impact.

CHECK failure is not a security bug, we fixed the parsing logic on clusterfuzz side, sorry for noise. this is legit functional bug though.

ClusterFuzz has detected this issue as fixed in range 489151:489186.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_asan_chrome
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  list_node in LayoutListItem.cpp
  blink::LayoutListItem::UpdateListMarkerNumbers
  blink::LayoutObjectChildList::RemoveChildNode
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=467203:467246
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=489151:489186

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


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

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