Issue metadata
Sign in to add a comment
|
Heap-use-after-free in base::sequence_manager::LazyNow::Now |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6120549869420544 Fuzzer: libFuzzer_sequence_manager_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Heap-use-after-free READ 8 Crash Address: 0x6140000005e0 Crash State: base::sequence_manager::LazyNow::Now base::sequence_manager::internal::ThreadControllerImpl::SetNextDelayedDoWork base::sequence_manager::internal::SequenceManagerImpl::SetNextDelayedDoWork Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=576884:576885 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6120549869420544 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jul 27
Automatically adding ccs based on suspected regression changelists: Scheduler: Fuzzer for TaskQueueManager V1. by farahcharab@google.com - https://chromium.googlesource.com/chromium/src/+/08b8303cdb8c6e0d355a8e3812c83f51b1a1d887 If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
,
Jul 27
,
Jul 27
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
,
Jul 27
,
Jul 27
ClusterFuzz has detected this issue as fixed in range 578657:578662. Detailed report: https://clusterfuzz.com/testcase?key=6120549869420544 Fuzzer: libFuzzer_sequence_manager_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Heap-use-after-free READ 8 Crash Address: 0x6140000005e0 Crash State: base::sequence_manager::LazyNow::Now base::sequence_manager::internal::ThreadControllerImpl::SetNextDelayedDoWork base::sequence_manager::internal::SequenceManagerImpl::SetNextDelayedDoWork Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=576884:576885 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=578657:578662 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6120549869420544 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.
,
Jul 27
ClusterFuzz testcase 6120549869420544 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jul 28
,
Aug 15
,
Nov 3
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 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Jul 27Labels: Test-Predator-Auto-Components