Issue metadata
Sign in to add a comment
|
Use-after-poison in blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5389141981528064 Fuzzer: inferno_layout_test_unmodified Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: Use-after-poison READ 8 Crash Address: 0x7e82ada19878 Crash State: blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue blink::scheduler::TaskQueueManager::DoWork Run Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=506675:506834 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5389141981528064 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 6 2017
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
,
Oct 6 2017
,
Oct 6 2017
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 6 2017
Looks similar to issue 772257. lpy, could you please take a look at this too?
,
Oct 6 2017
,
Nov 7 2017
,
Jan 16 2018
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 sheriffbot@chromium.org
, Oct 6 2017