Issue metadata
Sign in to add a comment
|
Stack-use-after-return in TDiagnostics::writeDebug |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4883370097246208 Fuzzer: libFuzzer_gpu_swiftshader_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Stack-use-after-return READ 8 Crash Address: 0x7f1c64489760 Crash State: TDiagnostics::writeDebug TParseContext::trace Trace Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=529108:529110 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4883370097246208 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jan 14 2018
,
Jan 14 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
,
Jan 14 2018
,
Jan 16 2018
ClusterFuzz has detected this issue as fixed in range 529251:529262. Detailed report: https://clusterfuzz.com/testcase?key=4883370097246208 Fuzzer: libFuzzer_gpu_swiftshader_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Stack-use-after-return READ 8 Crash Address: 0x7f1c64489760 Crash State: TDiagnostics::writeDebug TParseContext::trace Trace Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=529108:529110 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=529251:529262 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4883370097246208 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jan 16 2018
ClusterFuzz testcase 4883370097246208 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jan 16 2018
,
Feb 13 2018
,
Mar 27 2018
,
Apr 24 2018
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
, Jan 13 2018Labels: Test-Predator-Auto-Components