Automatically adding ccs based on suspected regression changelists:

Reland "Replace BundleFilter with RtpDemuxer in RtpTransport." by zhihuang@webrtc.org - https://webrtc.googlesource.com/src/+/27f3bf512827b483f9e0c67ce76362d83faa1950

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Fixing CL is out for review:
https://webrtc-review.googlesource.com/c/src/+/65340

Should have the same root cause as: https://bugs.chromium.org/p/chromium/issues/detail?id=826725

reverting the original change.

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Should be fixed now. The original CL has been reverted.

ClusterFuzz has detected this issue as fixed in range 546863:546887.

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

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x19d2de667600
Crash State:
  Bad-cast to rtc::PacketTransportInternal from content::(anonymous namespace)::IpcPacketSocket
  webrtc::RtpTransport::IsTransportWritable
  webrtc::RtpTransport::OnWritableState
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=546384:546391
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=546863:546887

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

Additional requirements: Requires HTTP

See https://github.com/google/clusterfuzz-tools 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 5089904347054080 is verified as fixed, so closing issue as verified.

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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