[llvm-bugs] Issue 18465 in oss-fuzz: llvm:clang-objc-fuzzer: Null-dereference READ in clang::ObjCMethodDecl::getOverriddenMethods

ClusterFuzz-External via monorail via llvm-bugs llvm-bugs at lists.llvm.org
Tue Oct 22 16:19:35 PDT 2019

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,  
igm... at gmail.com, davg at google.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 Reproducible Stability-Memory-MemorySanitizer  
Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-10-22
Type: Bug

New issue 18465 by ClusterFuzz-External: llvm:clang-objc-fuzzer:  
Null-dereference READ in clang::ObjCMethodDecl::getOverriddenMethods

Detailed Report: https://oss-fuzz.com/testcase?key=5070098498322432

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: clang-objc-fuzzer
Job Type: libfuzzer_msan_llvm
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:

Sanitizer: memory (MSAN)


Reproducer Testcase:  

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for  
instructions to reproduce this bug locally.
When you fix this bug, please
   * mention the fix revision(s).
   * state whether the bug was a short-lived regression or an old bug in any  
stable releases.
   * add any other useful information.
This information can help downstream consumers.

If you need to contact the OSS-Fuzz team with a question, concern, or any  
other feedback, please file an issue at  
https://github.com/google/oss-fuzz/issues. Comments on individual Monorail  
issues are not monitored.

You received this message because:
   1. You were specifically CC'd on the issue

You may adjust your notification preferences at:

Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20191022/2a2b0c0c/attachment.html>

More information about the llvm-bugs mailing list