Issue metadata
Sign in to add a comment
|
Crash in blink::CrossThreadPersistentRegion::ShouldTracePersistentNode |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6726197191639040 Fuzzer: inferno_layout_test_fuzzer Job Type: linux_ubsan_vptr_content_shell_drt Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x312306c01958 Crash State: blink::CrossThreadPersistentRegion::ShouldTracePersistentNode blink::PersistentRegion::TracePersistentNodes blink::ThreadState::VisitPersistents Sanitizer: undefined (UBSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=545879:545880 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6726197191639040 Additional requirements: Requires HTTP Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jun 1 2018
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
,
Jun 1 2018
,
Jun 1 2018
Only CL in regression range is https://chromium.googlesource.com/chromium/src/+/279708b3c8ed5b6d9b4ed452072458cb0f9047d0 lukasza: Can you PTAL as one of the reviewers? (also this is probably impact-none since it's in test code, but i'm leaving that unchanged for now)
,
Jun 2 2018
,
Jun 20 2018
lukasza: Uh oh! This issue still open and hasn't been updated in the last 19 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
,
Jun 28 2018
Who would be a good owner for this given that both vmpstr and lukasza are out?
,
Jun 29 2018
,
Jul 3
Bulk update: M68 stable cut is scheduled for July 19th. This issue is marked as RB-Stable, so please take a look at it before. Thanks!
,
Jul 4
trchen: Uh oh! This issue still open and hasn't been updated in the last 33 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
,
Jul 9
I'm not able to access the clusterfuzz report with either my chromium or google account. Shows "Invalid testcase.". Is it view restricted?
,
Jul 9
Hello meacer@, I couldn't access to the clusterfuzz report, could you check if it is permission error and assign back to us? Thanks!
,
Jul 9
Interesting, I'm getting the same error now (invalid testcase). mbarbella: Any thoughts why that would happen?
,
Jul 10
,
Jul 11
I wasn't able to find anything in our logs, but the most common thing that would cause this would be the test case being deleted manually. None of our automation should delete test cases associated with bugs (though if there's any other sign of that happening, file a bug with the Tools>Stability>ClusterFuzz component). I don't see anything open now with a similar stack, but this may have been a duplicate of issue 857311 .
,
Oct 18
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
, Jun 1 2018