From: "evv… via monorail" <monorail+v2.2672886254@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 43356 in oss-fuzz: elfutils:fuzz-dwfl-core: Misaligned-address in Elf32_cvt_Dyn
Date: Wed, 05 Jan 2022 18:03:42 -0800 [thread overview]
Message-ID: <00000000000093a49905d4e04733@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=1c666345e3f179e28b2ecb98f55737a7=oss-fuzz@monorail-prod.appspotmail.com>
Comment #1 on issue 43356 by evv...@gmail.com: elfutils:fuzz-dwfl-core: Misaligned-address in Elf32_cvt_Dyn
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43356#c1
It can be reproduced by downloading the reproducer testcase and passing it to eu-stack:
```
autoreconf -i -f
./configure --enable-maintainer-mode --enable-sanitize-address --enable-sanitize-undefined
make -j$(nproc) V=1
wget -O CRASH 'https://oss-fuzz.com/download?testcase_id=6013023414779904'
UBSAN_OPTIONS=print_stacktrace=1 LD_LIBRARY_PATH="./libdw;./libelf" ./src/stack --core CRASH
gelf_xlate.h:48:1: runtime error: member access within misaligned address 0x7f98edb0206a for type 'struct Elf32_Dyn', which requires 4 byte alignment
0x7f98edb0206a: note: pointer points here
20 20 20 00 00 00 8a 20 20 20 20 00 00 00 10 20 20 20 20 ff 20 20 20 ff ff ff ff 00 00 00 00 00
^
#0 0x7f98f23ef91f in Elf32_cvt_Dyn /home/vagrant/elfutils/libelf/gelf_xlate.h:48
#1 0x7f98f23ed9f9 in elf32_xlatetom /home/vagrant/elfutils/libelf/elf32_xlatetom.c:104
#2 0x7f98f20eac75 in dwfl_segment_report_module /home/vagrant/elfutils/libdwfl/dwfl_segment_report_module.c:848
#3 0x7f98f20f4ffd in _new.dwfl_core_file_report /home/vagrant/elfutils/libdwfl/core-file.c:563
#4 0x403b34 in parse_opt /home/vagrant/elfutils/src/stack.c:595
#5 0x7f98f1199471 in argp_parse (/lib64/libc.so.6+0x11e471)
#6 0x402a7d in main /home/vagrant/elfutils/src/stack.c:695
#7 0x7f98f10a855f in __libc_start_call_main (/lib64/libc.so.6+0x2d55f)
#8 0x7f98f10a860b in __libc_start_main_impl (/lib64/libc.so.6+0x2d60b)
#9 0x402f44 in _start (/home/vagrant/elfutils/src/stack+0x402f44)
```
--
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-06 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=1c666345e3f179e28b2ecb98f55737a7=oss-fuzz@monorail-prod.appspotmail.com>
2022-01-06 0:12 ` ClusterFuzz-External via monorail
2022-01-06 2:03 ` evv… via monorail [this message]
2022-01-08 16: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=00000000000093a49905d4e04733@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).