From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Cc: Evgeny Vereshchagin <evverx@gmail.com>,
Aleksei Vetrov <vvvvvv@google.com>
Subject: Fix some .debug checking and gnu hash xlate logic
Date: Mon, 20 Feb 2023 16:55:16 +0100 [thread overview]
Message-ID: <20230220155518.86598-1-mark@klomp.org> (raw)
Hi,
The last fuzzer found some use (checking) of undefine/uninitialized
data. Either of these two patches will fix that:
[PATCH 1/2] libelf: memmove any extra bytes left by elf_cvt_gnuhash
[PATCH 2/2] libdw: Use elf_rawdata when checking .debug section
Note that the bad data wouldn't actually be used, just checked for
validity. But these patches make sure the result is deterministic.
Cheers,
Mark
next reply other threads:[~2023-02-20 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 15:55 Mark Wielaard [this message]
2023-02-20 15:55 ` [PATCH 1/2] libelf: memmove any extra bytes left by elf_cvt_gnuhash conversion Mark Wielaard
2023-02-20 15:55 ` [PATCH 2/2] libdw: Use elf_rawdata when checking .debug section Mark Wielaard
2023-02-20 16:02 ` Aleksei Vetrov
2023-02-21 2:28 ` Evgeny Vereshchagin
2023-02-21 11:24 ` Mark Wielaard
2023-02-23 10:20 ` Mark Wielaard
2023-02-21 16:40 ` Aleksei Vetrov
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=20230220155518.86598-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=evverx@gmail.com \
--cc=vvvvvv@google.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).