Issue metadata
Sign in to add a comment
|
Use-of-uninitialized-value in mojo::edk::ChannelPosix::WriteNoLock |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4742723386212352 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: mojo::edk::ChannelPosix::WriteNoLock mojo::edk::ChannelPosix::Write mojo::edk::NodeChannel::SendChannelMessage Sanitizer: memory (MSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=489319:489347 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4742723386212352 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jul 26 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
,
Jul 26 2017
,
Jul 26 2017
(Security Sheriff Triage) rockot@-- this seems to have been caused by https://chromium-review.googlesource.com/584038 because that's the only mojo related CL in the regression range. If you aren't the right owner, please help find them or mark the bug as Untriaged.
,
Jul 26 2017
,
Jul 26 2017
This is Pri-0, crashing MSAN builds on startup and blocking fuzzing. Please fix soon or revert CL for now.
,
Jul 26 2017
The CL has already been reverted.
,
Jul 26 2017
,
Jul 27 2017
ClusterFuzz has detected this issue as fixed in range 489609:489658. Detailed report: https://clusterfuzz.com/testcase?key=4742723386212352 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: mojo::edk::ChannelPosix::WriteNoLock mojo::edk::ChannelPosix::Write mojo::edk::NodeChannel::SendChannelMessage Sanitizer: memory (MSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=489319:489347 Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=489609:489658 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4742723386212352 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jul 27 2017
ClusterFuzz testcase 4742723386212352 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jul 27 2017
,
Nov 2 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
, Jul 26 2017