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

In the regression range, maybe https://chromium.googlesource.com/chromium/src/+/2e591393c960659617b4907c5142f691b3578cce%5E%21/#F4 ?

Guessing https://chromium.googlesource.com/chromium/src/+/2e591393c960659617b4907c5142f691b3578cce per C4.

I am still having trouble reproducing the issue. I have sent an email to clusterfuzz-dev.

ClusterFuzz has detected this issue as fixed in range 496302:496333.

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

Fuzzer: inferno_flicker
Job Type: linux_asan_chrome_media
Platform Id: linux

Crash Type: Heap-use-after-free READ 8
Crash Address: 0x611000101ac0
Crash State:
  base::internal::Invoker<base::internal::BindState<long
  void base::internal::ReturnAsParamAdapter<long>
  base::internal::Invoker<base::internal::BindState<void
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=493893:493928
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_media&range=496302:496333

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

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

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

tguilbert: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

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

The issue no longer repros.

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.

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