From: "da… via monorail" <monorail+v2.1355924921@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 45646 in oss-fuzz: elfutils:fuzz-libdwfl: Misaligned-address in __libdw_image_header
Date: Sun, 20 Mar 2022 03:03:54 -0700 [thread overview]
Message-ID: <0000000000005b8f9005daa37f5e@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=1f7922c08a4ad559eae053cc22756846=oss-fuzz@monorail-prod.appspotmail.com>
Comment #1 on issue 45646 by da...@adalogics.com: elfutils:fuzz-libdwfl: Misaligned-address in __libdw_image_header
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45646#c1
UBSAN report
Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash-137c106fe516c3a5c4d5fb8deeb45c4e982d59a5
image-header.c:84:7: runtime error: load of misaligned address 0x7f2499144202 for type 'uint32_t' (aka 'unsigned int'), which requires 4 byte alignment
0x7f2499144202: note: pointer points here
55 aa 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
^
#0 0x4c04de in __libdw_image_header /src/elfutils/libdwfl/image-header.c:84:7
#1 0x4bf336 in libdw_open_elf /src/elfutils/libdwfl/open.c:141:15
#2 0x4bf1dc in __libdw_open_file /src/elfutils/libdwfl/open.c:197:10
#3 0x4b5e6d in __libdwfl_report_offline /src/elfutils/libdwfl/offline.c:281:22
#4 0x4b5e6d in dwfl_report_offline /src/elfutils/libdwfl/offline.c:316:10
#5 0x4b2f88 in LLVMFuzzerTestOneInput /src/fuzz-libdwfl.c:47:22
#6 0x43da32 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:611:15
#7 0x4295e2 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:324:6
#8 0x42ee4c in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:860:9
#9 0x4577e2 in main /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
#10 0x7f2498dd90b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/libc-start.c:308:16
#11 0x407d2d in _start
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior image-header.c:84:7 in
--
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-03-20 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=1f7922c08a4ad559eae053cc22756846=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 11:57 ` ClusterFuzz-External via monorail
2022-03-20 10:03 ` da… via monorail [this message]
2022-03-20 10:04 ` da… via monorail
2022-03-22 14:34 ` 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=0000000000005b8f9005daa37f5e@google.com \
--to=monorail+v2.1355924921@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).