Assigning to the concern owner from find it, below are the results,
Suspected CLs	The result is a list of CLs that change the crashed files.

Author: Sasi Inguva
Project: chromium-ffmpeg
Changelist: https://chromium.googlesource.com/chromium/third_party/ffmpeg.git/+/7e0235bdb145cf7975bda240acb629991c4b7048
Time: Tue Sep 27 01:41:01 2016
Lines 2378-2384 of file utils.c which potentially caused crash are changed in this cl (frame #5, "avcodec_decode_audio4").
Minimum distance from crash line to modified line: 0. (file: utils.c, crashed on: 2378, modified: 2378).

Suspected Project: chromium-ffmpeg

@Sasi Inguva -- Could you please take a look into the issue, kindly re-assign if this is not related to your change.
Thank You.

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

Had an offline chat with isasi@ and he would be able to look into this.

Thank you!

ClusterFuzz has detected this issue as fixed in range 477380:477461.

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

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  l3_unscale
  huffman_decode
  mp_decode_layer3
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=433019:433116
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=477380:477461

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


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.

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

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