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

kcwu: yet another :( Sorry for the barrage of bugs. Let us know if you need help triaging/finding owners.

ClusterFuzz has detected this issue as fixed in range 491766:491850.

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

Fuzzer: libFuzzer_media_vp9_parser_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  media::Vp9BoolDecoder::ConsumePaddingBits
  media::Vp9CompressedHeaderParser::Parse
  media::Vp9Parser::ParseNextFrame
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=485612:485661
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=491766:491850

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


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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