Issue metadata
Sign in to add a comment
|
Use-of-uninitialized-value in mojo::edk::ChannelPosix::WriteNoLock |
||||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=4611035590033408 Fuzzer: inferno_twister Job Type: linux_msan_content_shell_drt Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: mojo::edk::ChannelPosix::WriteNoLock mojo::edk::ChannelPosix::Write mojo::edk::NodeChannel::PortsMessage Recommended Security Severity: Medium Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_msan_content_shell_drt&range=416413:416450 Minimized Testcase (0.54 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96PRuAFJTyAtGCOVUc7d9p1g0VEtcyaO3pGw-z1enMGrt0jZufkZqAsl6iZ8Yr1OQEd1Q0jyjLYXTLH-Ev7pArv84XLqn5INcEQdGXNWFO4i6TSWUUMfPZZ9lxpoCL5-pkQcVTLIW_Vlf4vxHlx_EqgjGEAaA?testcase_id=4611035590033408 Additional requirements: Requires HTTP Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Sep 5 2016
,
Sep 5 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 5 2016
,
Sep 5 2016
Looking further down the stack, this was likely introduced by r416436. xlai@ could you please check if SubmitCompositorFrame() is being called with some uninitialized data?
,
Sep 5 2016
Friendly ping, this is currently a Beta-blocker and needs to get fixed and merged as soon as feasible, as M54 is going to beta this Thursday 9/8
,
Sep 6 2016
ClusterFuzz has detected this issue as fixed in range 416466:416526. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4611035590033408 Fuzzer: inferno_twister Job Type: linux_msan_content_shell_drt Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: mojo::edk::ChannelPosix::WriteNoLock mojo::edk::ChannelPosix::Write mojo::edk::NodeChannel::PortsMessage Recommended Security Severity: Medium Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_msan_content_shell_drt&range=416413:416450 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_msan_content_shell_drt&range=416466:416526 Minimized Testcase (0.54 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96PRuAFJTyAtGCOVUc7d9p1g0VEtcyaO3pGw-z1enMGrt0jZufkZqAsl6iZ8Yr1OQEd1Q0jyjLYXTLH-Ev7pArv84XLqn5INcEQdGXNWFO4i6TSWUUMfPZZ9lxpoCL5-pkQcVTLIW_Vlf4vxHlx_EqgjGEAaA?testcase_id=4611035590033408 Additional requirements: Requires HTTP 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 6 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Sep 6 2016
,
Dec 13 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 vakh@chromium.org
, Sep 5 2016Components: Infra>Client>Mojo Internals>Mojo
Owner: roc...@chromium.org
Status: Assigned (was: Untriaged)