Automatically adding ccs based on suspected regression changelists:

Skip H246 scaling lists in SPS packets by todd.wong.ndq@gmail.com - https://webrtc.googlesource.com/src/+/6728003bcf5657da8f9ed52ad84f46c1197ce54b

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

As per the below link assigning to the reviewer of the file.
https://webrtc-review.googlesource.com/c/src/+/36520

sprang@ Could you please take a look in to this issue?

Thanks!

ClusterFuzz has detected this issue as fixed in range 535947:535951.

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

Fuzzer: libFuzzer_h264_depacketizer_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  webrtc::SpsParser::ParseSpsUpToVui
  webrtc::SpsVuiRewriter::ParseAndRewriteSps
  webrtc::RtpDepacketizerH264::ProcessStapAOrSingleNalu
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=528024:528035
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=535947:535951

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

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 6505164143067136 is verified as fixed, so closing issue as verified.

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