From: "evv… via monorail" <monorail+v2.2672886254@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 43505 in oss-fuzz: elfutils:fuzz-dwfl-core: Use-of-uninitialized-value in handle_file_note
Date: Wed, 12 Jan 2022 14:37:03 -0800 [thread overview]
Message-ID: <00000000000070c35505d56a355b@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=2c0356afc660f9c3dfa1ade2a69ce6ad=oss-fuzz@monorail-prod.appspotmail.com>
Comment #3 on issue 43505 by evv...@gmail.com: elfutils:fuzz-dwfl-core: Use-of-uninitialized-value in handle_file_note
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43505#c3
Looking at another issue that hasn't been reported by OSS-Fuzz yet:
```
Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash-57876e6ee0a1504e6fa0b22336043846f283f4a2
==742==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x6374a5 in dwfl_segment_report_module /src/elfutils/libdwfl/dwfl_segment_report_module.c:401:11
#1 0x537d0d in dwfl_core_file_report /src/elfutils/libdwfl/core-file.c:563:17
#2 0x528aa5 in LLVMFuzzerTestOneInput /src/fuzz-dwfl-core.c:52:6
#3 0x455243 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) cxa_noexception.cpp:0
#4 0x440e92 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:324:6
#5 0x4466dc in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) cxa_noexception.cpp:0
#6 0x46f4a2 in main /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
#7 0x7f5d0ddbc0b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/libc-start.c:308:16
#8 0x41f60d in _start
Uninitialized value was created by an allocation of 'ehdr' in the stack frame of function 'dwfl_segment_report_module'
#0 0x62d610 in dwfl_segment_report_module /src/elfutils/libdwfl/dwfl_segment_report_module.c:301
```
it seems MSan doesn't like unions that aren't initialized explicitly
--
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 prev parent reply other threads:[~2022-01-12 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=2c0356afc660f9c3dfa1ade2a69ce6ad=oss-fuzz@monorail-prod.appspotmail.com>
2022-01-10 16:24 ` ClusterFuzz-External via monorail
2022-01-10 17:33 ` ClusterFuzz-External via monorail
2022-01-10 18:47 ` evv… via monorail
2022-01-12 22:37 ` evv… via monorail [this message]
2022-03-17 0:38 ` ClusterFuzz-External via monorail
2022-03-17 0:49 ` Mark Wielaard
2022-03-23 15:32 ` ClusterFuzz-External via monorail
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000070c35505d56a355b@google.com \
--to=monorail+v2.2672886254@chromium.org \
--cc=elfutils-devel@sourceware.org \
--cc=oss-fuzz@monorail-prod.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).