[llvm-bugs] Issue 19683 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::LookupResult::sanity

[ClusterFuzz-External via monorail via llvm-bugs]

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 Security_Severity-High  
Reported-2019-12-24
Type: Bug-Security

New issue 19683 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown  
address in clang::LookupResult::sanity
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19683

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

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

Crash Type: Segv on unknown address
Crash Address:
Crash State:
   clang::LookupResult::sanity
   clang::Sema::HandleDeclarator
   clang::Sema::ActOnDeclarator

Sanitizer: memory (MSAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=201911200438:201911230451

Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=4872329519955968

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:
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/20191223/f6fd59dc/attachment.html>