Issue metadata
Sign in to add a comment
|
Use-of-uninitialized-value in blink::TraceMethodDelegate<blink::PersistentBase<blink::DOMArrayBuffer, |
||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5373086939742208 Fuzzer: inferno_layout_test_unmodified Job Type: linux_msan_content_shell_drt Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: blink::TraceMethodDelegate<blink::PersistentBase<blink::DOMArrayBuffer, blink::PersistentRegion::tracePersistentNodes blink::ThreadState::visitPersistents Recommended Security Severity: Medium Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_msan_content_shell_drt&range=416899:416952 Minimized Testcase (7.41 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97n1yfDfA46-GoshzI5eXQDga4AwYsJQg-GC7cEmokkoCADSjZDVXzr36-RF26-C78UIsZm2r1yAGg52Wo8PHr6GjSqIhOjAkLvD8ka5mGdly7-qC4A4RZyvDPfvMvD62KO2k2VmsdVpbCcWy8ryk6X87Lfxg?testcase_id=5373086939742208 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Sep 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
,
Sep 8 2016
,
Sep 8 2016
Hi, it looks like https://codereview.chromium.org/2304023003 moved StackFrameDepth from a static global to a heap-allocated structure (ThreadHeap), which results in m_stackFrameLimit being uninitialized - mind taking a look at this, keishi@?
,
Sep 9 2016
,
Sep 9 2016
,
Sep 10 2016
ClusterFuzz has detected this issue as fixed in range 417414:417566. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5373086939742208 Fuzzer: inferno_layout_test_unmodified Job Type: linux_msan_content_shell_drt Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: blink::TraceMethodDelegate<blink::PersistentBase<blink::DOMArrayBuffer, blink::PersistentRegion::tracePersistentNodes blink::ThreadState::visitPersistents Recommended Security Severity: Medium Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_msan_content_shell_drt&range=416899:416952 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_msan_content_shell_drt&range=417414:417566 Minimized Testcase (7.41 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97n1yfDfA46-GoshzI5eXQDga4AwYsJQg-GC7cEmokkoCADSjZDVXzr36-RF26-C78UIsZm2r1yAGg52Wo8PHr6GjSqIhOjAkLvD8ka5mGdly7-qC4A4RZyvDPfvMvD62KO2k2VmsdVpbCcWy8ryk6X87Lfxg?testcase_id=5373086939742208 See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Sep 10 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Sep 10 2016
,
Oct 7 2016
keishi@, any idea which change fixed this?
,
Oct 10 2016
,
Dec 17 2016
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
, Sep 8 2016