[llvm-bugs] Issue 15534 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_unroll: Null-dereference READ in BitcodeReader::parseFunctionBody
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Fri Jun 28 16:52:12 PDT 2019
Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,
igm... at gmail.com, mitchp at google.com, bigchees... at gmail.com,
eneyman at google.com, llvm-b... at lists.llvm.org, jfb at chromium.org,
v... at apple.com, mitchphi... at outlook.com, xpl... at gmail.com,
akils... at apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible
Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-06-28
Type: Bug
New issue 15534 by ClusterFuzz-External:
llvm/llvm-opt-fuzzer--x86_64-loop_unroll: Null-dereference READ in
BitcodeReader::parseFunctionBody
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15534
Detailed report: https://oss-fuzz.com/testcase?key=5685841600446464
Project: llvm
Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-loop_unroll
Fuzz target binary: llvm-opt-fuzzer--x86_64-loop_unroll
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
BitcodeReader::parseFunctionBody
BitcodeReader::materialize
BitcodeReader::materializeModule
Sanitizer: address (ASAN)
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201906270304:201906280305
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5685841600446464
Issue filed automatically.
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for
instructions to reproduce this bug locally.
--
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190628/e303d746/attachment.html>
More information about the llvm-bugs
mailing list