From: "da… via monorail" <monorail+v2.1355924921@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 45682 in oss-fuzz: elfutils:fuzz-libelf: Misaligned-address in elf_cvt_Verneed
Date: Sun, 20 Mar 2022 03:04:54 -0700 [thread overview]
Message-ID: <000000000000e47d2805daa382d9@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=a85441926cb00ec9ce25fb4e2b57efdb=oss-fuzz@monorail-prod.appspotmail.com>
Comment #1 on issue 45682 by da...@adalogics.com: elfutils:fuzz-libelf: Misaligned-address in elf_cvt_Verneed
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45682#c1
UBSAN report
Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash-cf18cd9802d6953b96a96cb2364e46ade2dccddc
version_xlate.h:204:22: runtime error: member access within misaligned address 0x000002dfee46 for type 'GElf_Vernaux' (aka 'Elf64_Vernaux'), which requires 4 byte alignment
0x000002dfee46: note: pointer points here
4c 46 01 02 01 20 00 00 00 04 20 20 20 20 00 00 00 02 20 20 20 20 20 20 20 20 20 20 20 20 00 00
^
#0 0x4c63b6 in elf_cvt_Verneed /src/elfutils/libelf/version_xlate.h:204:22
#1 0x4be96f in convert_data /src/elfutils/libelf/elf_getdata.c:192:7
#2 0x4be96f in __libelf_set_data_list_rdlock /src/elfutils/libelf/elf_getdata.c:453:7
#3 0x4bf17e in __elf_getdata_rdlock /src/elfutils/libelf/elf_getdata.c:560:5
#4 0x4bf39e in elf_getdata /src/elfutils/libelf/elf_getdata.c:578:12
#5 0x4c2d88 in elf_compress_gnu /src/elfutils/libelf/elf_compress_gnu.c:150:24
#6 0x4b2e03 in fuzz_logic_one /src/fuzz-libelf.c:48:15
#7 0x4b303f in LLVMFuzzerTestOneInput /src/fuzz-libelf.c:81:3
#8 0x43d812 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:611:15
#9 0x4293c2 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:324:6
#10 0x42ec2c in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:860:9
#11 0x4575c2 in main /src/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:10
#12 0x7f20c9b5d0b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/libc-start.c:308:16
#13 0x407b0d in _start
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior version_xlate.h:204:22 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:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=a85441926cb00ec9ce25fb4e2b57efdb=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 20:15 ` ClusterFuzz-External via monorail
2022-03-20 10:04 ` da… via monorail [this message]
2022-03-20 10:05 ` da… via monorail
2022-03-22 14:22 ` 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=000000000000e47d2805daa382d9@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).