From: "mark at klomp dot org" <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: Fri, 24 Dec 2021 01:10:13 +0000 [thread overview]
Message-ID: <bug-28720-10460-xTytVUkalW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28720-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28720
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at sourceware dot org |mark at klomp dot org
Last reconfirmed| |2021-12-24
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Evgeny Vereshchagin from comment #1)
> FWIW There are at least 4 uniq crashes honggfuzz has found related to either
> "member access within misaligned address" or "load of misaligned address":
>
> gelf_xlate.h:42:1: runtime error: member access within misaligned address
>
> link_map.c:292:15: runtime error: load of misaligned address 0x7fffe5c60bde
> for type 'Elf64_Addr'
>
> link_map.c:283:15: runtime error: load of misaligned address
>
> gelf_xlate.h:48:1: runtime error: member access within misaligned address
Interesting. I did run afl for some time (more than a day) and it found some
more issues, but none of these (yet?). I'll try honggfuzz in the future to see
if it can find some more.
Without reproducers for all of the above I don't know if I caught them all, but
I think the following two proposed patches (also on my fuzz branch) should fix
them:
https://sourceware.org/pipermail/elfutils-devel/2021q4/004598.html
https://sourceware.org/pipermail/elfutils-devel/2021q4/004599.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-24 1:10 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 [this message]
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
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-xTytVUkalW@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).