Issue metadata
Sign in to add a comment
|
Heap-use-after-free in blink::LayoutBlockFlow::XPositionForFloatIncludingMargin |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5157406418665472 Fuzzer: inferno_layout_test_unmodified Job Type: linux_asan_chrome_v8_arm Platform Id: linux Crash Type: Heap-use-after-free READ 4 Crash Address: 0xf2276780 Crash State: blink::LayoutBlockFlow::XPositionForFloatIncludingMargin blink::LayoutBlockFlow::AddOverflowFromFloats blink::LayoutBlockFlow::ComputeOverflow Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=544339:544340 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5157406418665472 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
May 1 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/483aa2ccff1595fba505304cccd661c5384fa6b3 (Hide implementations of ScopedAllowIO/ScopedAllowWait like other scoped thread restrictions objects). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
May 1 2018
,
May 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
,
May 1 2018
,
May 1 2018
,
May 1 2018
ClusterFuzz has detected this issue as fixed in range 555009:555014. Detailed report: https://clusterfuzz.com/testcase?key=5157406418665472 Fuzzer: inferno_layout_test_unmodified Job Type: linux_asan_chrome_v8_arm Platform Id: linux Crash Type: Heap-use-after-free READ 4 Crash Address: 0xf2276780 Crash State: blink::LayoutBlockFlow::XPositionForFloatIncludingMargin blink::LayoutBlockFlow::AddOverflowFromFloats blink::LayoutBlockFlow::ComputeOverflow Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=544339:544340 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=555009:555014 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5157406418665472 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.
,
Aug 8
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 ClusterFuzz
, May 1 2018Labels: Test-Predator-Auto-Components