Null-dereference READ in s_DCTD_process |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6041891273179136 Fuzzer: libFuzzer_chromeos_gstoraster_fuzzer Job Type: libfuzzer_asan_chromeos Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: s_DCTD_process sreadbuf s_process_read_buf Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=3138110:3138341 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6041891273179136 Issue filed automatically. See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for more information.
,
Nov 27
,
Nov 28
,
Dec 1
ClusterFuzz testcase 6041891273179136 appears to be flaky, updating reproducibility label.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 4
ClusterFuzz testcase 6041891273179136 appears to be flaky, updating reproducibility label.
,
Dec 4
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This was caused by another bug in ClusterFuzz that has been fixed. Sorry again for the inconvenience.
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ClusterFuzz
, Nov 24Labels: ClusterFuzz-Auto-CC