Issue metadata
Sign in to add a comment
|
Crash in content::RunCallbacks |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6754680080957440 Fuzzer: inferno_layout_test_unmodified Job Type: linux_ubsan_vptr_chrome Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x221100000003 Crash State: content::RunCallbacks content::StatusCallbackAdapter content::FileSystemDispatcher::~FileSystemDispatcher Sanitizer: undefined (UBSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=580345:580346 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6754680080957440 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Aug 3
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/104d9bf8175d3ec3feb862cee68808c57ce575af (Mojofy FileSystem). 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.
,
Aug 3
,
Aug 3
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
,
Aug 3
,
Aug 4
ClusterFuzz has detected this issue as fixed in range 580528:580530. Detailed report: https://clusterfuzz.com/testcase?key=6754680080957440 Fuzzer: inferno_layout_test_unmodified Job Type: linux_ubsan_vptr_chrome Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x221100000003 Crash State: content::RunCallbacks content::StatusCallbackAdapter content::FileSystemDispatcher::~FileSystemDispatcher Sanitizer: undefined (UBSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=580345:580346 Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=580528:580530 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6754680080957440 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 4
ClusterFuzz testcase 6754680080957440 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Aug 4
,
Aug 15
,
Nov 10
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
, Aug 3Labels: Test-Predator-Auto-Components