[llvm-bugs] Issue 12488 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Lexer::LexTokenInternal

[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, 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 Proj-llvm Reported-2019-01-13
Type: Bug

New issue 12488 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow  
in clang::Lexer::LexTokenInternal
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12488

Detailed report: https://oss-fuzz.com/testcase?key=5737567926878208

Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Fuzz target binary: clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffd6a671e60
Crash State:
   clang::Lexer::LexTokenInternal
   clang::Lexer::Lex
   clang::Preprocessor::Lex

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901080410:201901090413

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

Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md 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.

-- 
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/20190112/d68a5fa4/attachment.html>