Hi, On Thu, Aug 21, 2025 at 01:14:38AM -0700, buganizer-sys...@google.com wrote: > Replying to this email means your email address will be shared with the > team that works on this product. > https://issues.oss-fuzz.com/issues/440144412
This (and the similar emails sent recently) isn't really enough information to understand what you are testing/fuzzing. Could you just show the test/fuzz program and full backtrace? > Reference Info: 440144412 elfutils:fuzz-libdwfl: Check failed in CheckUnwind > component: Public Trackers > 1362134 > OSS Fuzz > status: New > reporter: 87...@developer.gserviceaccount.com > cc: da...@adalogics.com, elfutils-devel@sourceware.org, ev...@gmail.com, > and 1 more > collaborators: co...@oss-fuzz.com > type: Vulnerability > access level: Default access > priority: P2 > severity: S1 > hotlist: Reproducible, Stability-Memory-MemorySanitizer > retention: Component default > Project: elfutils > Reported: Aug 21, 2025 > > 87...@developer.gserviceaccount.com added comment #1: > Detailed Report: https://oss-fuzz.com/testcase?key=5624595337248768 > > Project: elfutils > Fuzzing Engine: libFuzzer > Fuzz Target: fuzz-libdwfl > Job Type: libfuzzer_msan_elfutils > Platform Id: linux > > Crash Type: Check failed > Crash Address: > Crash State: > CheckUnwind > elf_end > libdw_open_elf > > Sanitizer: memory (MSAN) > > Regressed: > https://oss-fuzz.com/revisions?job=libfuzzer_msan_elfutils&range=202508201802:202508210000 > > Reproducer Testcase: > https://oss-fuzz.com/download?testcase_id=5624595337248768 > > 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. > > > Generated by Google IssueTracker notification system.
