Issue metadata
Sign in to add a comment
|
Use-after-poison in void blink::TraceTrait<blink::HeapHashTableBacking<WTF::HashTable<blink::WeakMem |
||||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5303118642544640 Fuzzer: inferno_twister Job Type: linux_asan_chrome_v8_arm Platform Id: linux Crash Type: Use-after-poison READ 4 Crash Address: 0xb2228270 Crash State: void blink::TraceTrait<blink::HeapHashTableBacking<WTF::HashTable<blink::WeakMem blink::ThreadHeap::processMarkingStack blink::ThreadState::collectGarbage Recommended Security Severity: High Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=419134:419140 Minimized Testcase (26.87 Kb): https://cluster-fuzz.appspot.com/download/AMIfv964aY_-ESzb7j-3fTli0RqxKxLoV-KXao_F5mEU13vzhwrYk4W7GAlB9WSMx90j2ZmNq74spNa35VL-L8P198uaNU3Tr-bWb-eOP7-5qh10R2uQHi3lS9Xn_JmZ2_EizubBYL-gqCZUhzr7jWLgZaF42LRdsp3BRscT8K-ADXNedFwVexY?testcase_id=5303118642544640 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Nov 7 2016
,
Nov 8 2016
lpy can you take a look? The regressed range is inconclusive -- this is probably a preexisting bug that was uncovered by a memory layout change in 56.0.2885.0
,
Nov 8 2016
I am not sure about it, since I don't have recent changes related to it if I understand correctly. Deassign myself, reassign to mlippautz@ who is one of the experts in V8 GC, also cc hpayer@.
,
Nov 8 2016
,
Nov 8 2016
,
Nov 8 2016
,
Nov 8 2016
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 16 2016
keishi: Uh oh! This issue still open and hasn't been updated in the last 14 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
,
Nov 30 2016
keishi: Uh oh! This issue still open and hasn't been updated in the last 28 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
,
Dec 1 2016
No longer reproducible, and not seeing any new instances of it on CF. Closing...
,
Mar 10 2017
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
, Nov 2 2016