New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 868203 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Jul 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Heap-use-after-free in base::sequence_manager::LazyNow::Now

Project Member Reported by ClusterFuzz, Jul 27

Issue description

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

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.
 
Project Member

Comment 1 by ClusterFuzz, Jul 27

Components: Internals>TaskScheduler
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Jul 27

Cc: farahcharab@google.com
Labels: Test-Predator-Auto-CC
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.
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 27

Labels: M-69 Target-69
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 27

Labels: ReleaseBlock-Stable
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
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 27

Labels: Pri-1
Project Member

Comment 6 by ClusterFuzz, 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.
Project Member

Comment 7 by ClusterFuzz, Jul 27

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
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.
Project Member

Comment 8 by sheriffbot@chromium.org, Jul 28

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -ReleaseBlock-Stable
Project Member

Comment 10 by sheriffbot@chromium.org, Nov 3

Labels: -Restrict-View-SecurityNotify allpublic
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