From: "evv… via monorail" <monorail+v2.2672886254@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 43307 in oss-fuzz: elfutils:fuzz-dwfl-core: Crash in read_addrs
Date: Wed, 05 Jan 2022 18:06:47 -0800 [thread overview]
Message-ID: <0000000000009ab21605d4e05269@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=3ce60818595e4317dc54eac606c643ef=oss-fuzz@monorail-prod.appspotmail.com>
Comment #2 on issue 43307 by evv...@gmail.com: elfutils:fuzz-dwfl-core: Crash in read_addrs
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43307#c2
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 oss-fuzz-43307 'https://oss-fuzz.com/download?testcase_id=4696722113167360'
LD_LIBRARY_PATH="./libdw;./libelf" ./src/stack --core ./oss-fuzz-43307
AddressSanitizer:DEADLYSIGNAL
=================================================================
==159086==ERROR: AddressSanitizer: SEGV on unknown address 0x7f1c426f6fe0 (pc 0x7f1c47758399 bp 0x60b000001170 sp 0x7ffdf9aca7a0 T0)
==159086==The signal is caused by a READ memory access.
#0 0x7f1c47758399 in read_8ubyte_unaligned_noncvt ../libdw/memory-access.h:301
#1 0x7f1c47758399 in read_addrs /home/vagrant/elfutils/libdwfl/link_map.c:288
#2 0x7f1c47758399 in report_r_debug /home/vagrant/elfutils/libdwfl/link_map.c:341
#3 0x7f1c47758399 in dwfl_link_map_report /home/vagrant/elfutils/libdwfl/link_map.c:1117
#4 0x7f1c4775df31 in _new.dwfl_core_file_report /home/vagrant/elfutils/libdwfl/core-file.c:552
#5 0x403b34 in parse_opt /home/vagrant/elfutils/src/stack.c:595
#6 0x7f1c46802471 in argp_parse (/lib64/libc.so.6+0x11e471)
#7 0x402a7d in main /home/vagrant/elfutils/src/stack.c:695
#8 0x7f1c4671155f in __libc_start_call_main (/lib64/libc.so.6+0x2d55f)
#9 0x7f1c4671160b in __libc_start_main_impl (/lib64/libc.so.6+0x2d60b)
#10 0x402f44 in _start (/home/vagrant/elfutils/src/stack+0x402f44)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV ../libdw/memory-access.h:301 in read_8ubyte_unaligned_noncvt
==159086==ABORTING
```
--
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:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=3ce60818595e4317dc54eac606c643ef=oss-fuzz@monorail-prod.appspotmail.com>
2022-01-04 18:02 ` ClusterFuzz-External via monorail
2022-01-04 19:05 ` ClusterFuzz-External via monorail
2022-01-06 2:06 ` evv… via monorail [this message]
2022-01-08 15:54 ` 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=0000000000009ab21605d4e05269@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).