Predator and CL could not provide any possible suspects.
Using the code search for the file, “source_buffer_range_by_pts.cc” assigning to concern owner.
Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/5356f74e8106352af92d016155f61d6f629c172f

@wolenetz -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thank You.

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

ClusterFuzz has detected this issue as fixed in range 512987:513015.

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

Fuzzer: libFuzzer_mediasource_MP4_AACLC_AVC_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  media::SourceBufferRangeByPts::GetBufferIndexAt
  media::SourceBufferRangeByPts::TruncateAt
  media::SourceBufferStream<media::SourceBufferRangeByPts>::RemoveInternal
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=508791:508824
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=512987:513015

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.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 5340160932970496 is verified as fixed, so closing issue as verified.

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