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

Seems like another from https://chromium.googlesource.com/chromium/src/+/3431b89c8be2d7b1a60f5eb135b1d27ce432ce9b

ClusterFuzz has detected this issue as fixed in range 557119:557122.

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  blink::LayoutSVGResourceFilter::RemoveClientFromCache
  blink::SVGResources::RemoveClientFromCacheAffectingObjectBounds
  blink::LayoutSVGResourceContainer::MarkForLayoutAndParentResourceInvalidation
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=556742:556743
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=557119:557122

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

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

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