From: "evvers at ya dot ru" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/28720] UBSan: member access within misaligned address 0x7f6e8d80f142 for type 'struct Elf32_Phdr', which requires 4 byte alignment
Date: Tue, 04 Jan 2022 19:21:59 +0000 [thread overview]
Message-ID: <bug-28720-10460-7NefstXHM9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28720-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28720
--- Comment #9 from Evgeny Vereshchagin <evvers at ya dot ru> ---
According to OSS-Fuzz looks like that commit triggered
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43307 (which was also
reported in
https://sourceware.org/pipermail/elfutils-devel/2022q1/004623.html):
```
$ wget -O CRASH 'https://oss-fuzz.com/download?testcase_id=4696722113167360'
$ LD_LIBRARY_PATH="./libdw;./libelf" ./src/stack --core ./CRASH
AddressSanitizer:DEADLYSIGNAL
=================================================================
==153072==ERROR: AddressSanitizer: SEGV on unknown address 0x7fbe8640afe0 (pc
0x7fbe89eb2fc7 bp 0x7fffe2855510 sp 0x7fffe2855020 T0)
==153072==The signal is caused by a READ memory access.
#0 0x7fbe89eb2fc7 in __bswap_64 /usr/include/bits/byteswap.h:73
#1 0x7fbe89eb2fc7 in read_addrs
/home/vagrant/elfutils/libdwfl/link_map.c:288
#2 0x7fbe89eb2fc7 in report_r_debug
/home/vagrant/elfutils/libdwfl/link_map.c:341
#3 0x7fbe89eb2fc7 in dwfl_link_map_report
/home/vagrant/elfutils/libdwfl/link_map.c:1117
#4 0x7fbe89eb7103 in _new.dwfl_core_file_report
/home/vagrant/elfutils/libdwfl/core-file.c:552
#5 0x403d06 in parse_opt /home/vagrant/elfutils/src/stack.c:595
#6 0x7fbe89a90471 in argp_parse (/lib64/libc.so.6+0x11e471)
#7 0x40281d in main /home/vagrant/elfutils/src/stack.c:695
#8 0x7fbe8999f55f in __libc_start_call_main (/lib64/libc.so.6+0x2d55f)
#9 0x7fbe8999f60b in __libc_start_main_impl (/lib64/libc.so.6+0x2d60b)
#10 0x402c94 in _start (/home/vagrant/elfutils/src/stack+0x402c94)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /usr/include/bits/byteswap.h:73 in __bswap_64
==153072==ABORTING
```
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-04 19:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 0:35 [Bug libdw/28720] New: " evvers at ya dot ru
2021-12-22 1:00 ` [Bug libdw/28720] " evvers at ya dot ru
2021-12-24 1:10 ` mark at klomp dot org
2021-12-24 8:05 ` evvers at ya dot ru
2021-12-24 8:06 ` evvers at ya dot ru
2021-12-24 8:07 ` evvers at ya dot ru
2021-12-24 8:17 ` evvers at ya dot ru
2022-01-03 23:42 ` mark at klomp dot org
2022-01-04 18:58 ` evvers at ya dot ru
2022-01-04 19:21 ` evvers at ya dot ru [this message]
2022-01-04 21:37 ` mark at klomp dot org
2022-01-04 22:02 ` evvers at ya dot ru
2022-01-06 0:51 ` evvers at ya dot ru
2022-01-06 15:55 ` mark at klomp dot org
2022-01-06 16:41 ` mark at klomp dot org
2022-01-06 17:04 ` mark at klomp dot org
2022-01-06 17:36 ` evvers at ya dot ru
2022-01-06 20:52 ` evvers at ya dot ru
2022-01-07 16:39 ` mark at klomp dot org
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=bug-28720-10460-7NefstXHM9@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/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).