haraken@, I wonder if you can take a look at this and/or if you know who can fix this crash. Thank you.

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

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

haraken: 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

ClusterFuzz has detected this issue as fixed in range 464942:464964.

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

Fuzzer: v8_builtins_generator
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  blink::Notification::prepareShow
  blink::TimerBase::runInternal
  base::debug::TaskAnnotator::RunTask
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=412760:412915
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=464942:464964

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95XmxWQpFrt6BGK0RcoaUvrc_1isj4iws6kENJq8B9DXLRGfYLyZ4AlZdfwTgMCs0RxskaU8z3b0GgJcgx2bvmkwnGVNbCgnRVr2qwhnoPtECe_hj0H4OsJ3XuD-cBwokobTEkdcIRio3u0OPZuR8cNYHiuOwKI0TOSamEH2DDKJKIDeYfvRhfCv4Jxl4-C0d70KTbDDtSTAvo_Dh6vYgFdF2cFC-zwTHkU18KeiseFa75ztlpgy5c8Qig-7AgBzOTfIlNCELBabbbPvjBpHm2QWR-tKWK7FywK7rF1keARp0JFAEYLeatjrdFMDRrnI7hpkypJc35CXHuUpLE5Od6C-nfLmdR-OmESkAy9rIY7KFtDHfZko8PIZIfl1d4krThPqkO39fRGs3ztU9ZxSjxsE2yaug?testcase_id=5795189756264448


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 5795189756264448 is verified as fixed, so closing issue.

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