As per regression range assigning to the owner of the CL
https://chromium.googlesource.com/chromium/src/+/cfd33cef4f1a51ba612d28504c6f76e1dfe588a6

wolenetz@, could you please take a look and help us to find correct owner if it is not related your changes.

=> liberato@ who will be doing the M-57 ffmpeg roll.
Note, depending on severity, the fix might need to merge to M56.

ClusterFuzz has detected this issue as fixed in range 435261:438085.

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  sign_extend
  get_sbits_long
  decode_residuals
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=433020:433158
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=435261:438085

Minimized Testcase (6862.26 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95uj57l0mQMdqPCP-qJ8HpCa5JqamYjMRVoEHv8mcLIs8f2A6AiBn3AzEcNZamD-3cTWuIpIno2t0ZwqNc1PM_nZDg1h04ChhOybhuiBnypF5VsDA61-ci2T5a7augBB4FRPffVfU9eVS8RudFIMfaLk8aIn3WvNjDjsBgknWtZVXA3XB8?testcase_id=6219461351964672

Additional requirements: Requires HTTP

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.

ClusterFuzz testcase 6219461351964672 is verified as fixed, so closing issue.

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

Though the paths leading to get_sbits_long differ, the specific failure looks like it was fixed by the change that fixed issue 640889 (https://bugs.chromium.org/p/chromium/issues/detail?id=640889#c7).

I've already merged that fix to M56 (https://bugs.chromium.org/p/chromium/issues/detail?id=640889#c17) and added an FFmpegRegressionTest (https://bugs.chromium.org/p/chromium/issues/detail?id=640889#c15) in the other repro case.