Null-dereference READ in spirv_cross::Compiler::parse |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5648488393867264 Fuzzer: libFuzzer_dawn_spirv_cross_msl_fast_fuzzer Fuzz target binary: dawn_spirv_cross_msl_fast_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: spirv_cross::Compiler::parse spirv_cross::CompilerGLSL::CompilerGLSL DawnSPIRVCrossFuzzer::ExecuteWithSignalTrap Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=609741:609751 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5648488393867264 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Dec 21
Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/fbeca676d409ec19572e3299288f4010c2ee8fd5 (Tighten when signal trap is used in SPIRV-Cross fuzzers). 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.
,
Dec 21
ClusterFuzz has detected this issue as fixed in range 618425:618430. Detailed report: https://clusterfuzz.com/testcase?key=5648488393867264 Fuzzer: libFuzzer_dawn_spirv_cross_msl_fast_fuzzer Fuzz target binary: dawn_spirv_cross_msl_fast_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: spirv_cross::Compiler::parse spirv_cross::CompilerGLSL::CompilerGLSL DawnSPIRVCrossFuzzer::ExecuteWithSignalTrap Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=609741:609751 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=618425:618430 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5648488393867264 See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Dec 21
ClusterFuzz testcase 5648488393867264 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Dec 21Labels: ClusterFuzz-Auto-CC