Issue metadata
Sign in to add a comment
|
Heap-use-after-free in scoped_refptr<base::sequence_manager::internal::AssociatedThreadId>::operator-> |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4588024487477248 Fuzzer: libFuzzer_sequence_manager_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Heap-use-after-free READ 8 Crash Address: 0x60b0000086a8 Crash State: scoped_refptr<base::sequence_manager::internal::AssociatedThreadId>::operator-> base::sequence_manager::TaskQueue::IsOnMainThread base::sequence_manager::TaskQueue::AcquireImplReadLockIfNeeded Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=588004:588005 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4588024487477248 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Sep 1
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/61246e800ddcedbe739b80e99e75777214b7e71a ([iOS][MF] Password view controller). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Sep 1
,
Sep 2
This class isn't yet instantiated at any point. Can't be the cause.
,
Sep 2
,
Sep 2
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
,
Sep 2
,
Sep 5
,
Sep 7
Hi @farahcharab, assigning to you since you wrote most of the code involved in the stack traces and allocator stacks.
,
Sep 7
Noting that this is probably the same bug as issue 880243 , which did pick out the correct buggy CL (I think).
,
Sep 7
@altimin (farahcharab@ is no longer active I believe)
,
Sep 14
ClusterFuzz testcase 4588024487477248 appears to be flaky, updating reproducibility label.
,
Sep 14
ClusterFuzz testcase 4588024487477248 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Dec 22
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
, Sep 1Labels: Test-Predator-Auto-Components