From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/29000] Conditional jump or move depends on uninitialised value in elf_compress_gnu
Date: Fri, 25 Mar 2022 13:01:38 +0000 [thread overview]
Message-ID: <bug-29000-10460-Ok518GtweT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29000-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29000
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |mark at klomp dot org
Ever confirmed|0 |1
Last reconfirmed| |2022-03-25
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
That is interesting, it seems to occur because the section is decompressed
twice (and fails). Apparently elf_getdata leaves some uninitialized data around
the first time, which gets picked up (and checked) the second time.
This can only happen when using elf_compress_gnu because we cannot tell whether
or not the data is already (de)compressed (it is a convention based on the
section name, instead of using a proper section flag).
It can also be triggered on the second example with valgrind eu-readelf -w
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-03-25 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 0:09 [Bug libelf/29000] New: " evvers at ya dot ru
2022-03-25 11:17 ` [Bug libelf/29000] " evvers at ya dot ru
2022-03-25 13:01 ` mark at klomp dot org [this message]
2022-03-29 22:35 ` mark at klomp dot org
2022-03-30 10:06 ` evvers at ya dot ru
2022-03-30 14:48 ` 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-29000-10460-Ok518GtweT@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).