Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically adding ccs based on suspected regression changelists:

Make RtpGenericFrameDescriptor available for E2EE. by philipel@webrtc.org - https://webrtc.googlesource.com/src/+/2837edce997b469a702bb96f84ac49dfb727531d

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

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

I can download the test case but not see the details of the crash (no permissions). I can't reproduce the crash on ToT.

Ran the repro steps found in the details of the crash, and it has not yet caught up with WebRTC ToT. The fix landed here solves this problem: https://webrtc-review.googlesource.com/c/src/+/103462

This is not a crash in production code, just in fuzzing.

I can't set this bug to "fixed" though since I can't access it from my @chromium account for some reason.

ClusterFuzz has detected this issue as fixed in range 596655:596661.

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

Fuzzer: libFuzzer_packet_buffer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN WRITE
Crash Address: 0xffffffffffffffef
Crash State:
  AtomicallySetQuarantineFlagIfAllocated
  webrtc::RtpGenericFrameDescriptor::~RtpGenericFrameDescriptor
  absl::optional_internal::optional_data_dtor_base<webrtc::RtpGenericFrameDescript
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=595906:595916
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=596655:596661

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

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 6615545468944384 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