I'm marking this as a duplicate of  issue 603485 . If I read the cluster-fuzz report correctly, it lists "Chromium: 386980". The fix for 603485 went in as #387505, so this bot is running older code.

ClusterFuzz has detected this issue as fixed in range 387029:388415.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4555907874160640

Fuzzer: libfuzzer_media_h264_parser_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  media::H264BitReader::UpdateCurrByte
  media::H264BitReader::ReadBits
  media::H264Parser::ParseSPS
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=386932:386961
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=387029:388415

Minimized Testcase (1.24 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97N2W8OXkJteCfUW8jxeowceP77nWQ-8yNqB6-SofO7MeONzrDXO4kcFXlY-F0CNg2ODKtfSUDuKBaSSQ0A0C-veCtak7S9jfgt74FRA64-W7zh9SjXSkkxCSw41mnGF1dz5I8DAISFzAOLYCGaT4nSQOWWKw

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

jrummell@, you are definitely right! Build was broken for some time, so CF was dealing with older builds.

Sorry for duplication, my bad.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot