From: "ago at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/21301] New: memory allocation failure in __libelf_decompress
Date: Fri, 24 Mar 2017 09:20:00 -0000 [thread overview]
Message-ID: <bug-21301-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=21301
Bug ID: 21301
Summary: memory allocation failure in __libelf_decompress
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libelf
Assignee: unassigned at sourceware dot org
Reporter: ago at gentoo dot org
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Created attachment 9938
--> https://sourceware.org/bugzilla/attachment.cgi?id=9938&action=edit
stacktrace
AN IMPORTANT NOTE:
as the stacktrace said this can be a false positive, so if you think that there
isn't anything to fix, feel free to close.
On elfutils-0.168:
# eu-readelf -a $FILE
==1927==WARNING: AddressSanitizer failed to allocate 0x280065041580 bytes
#5 0x7f85fb88dd1e in __libelf_decompress
/tmp/portage/dev-libs/elfutils-0.168/work/elfutils-0.168/libelf/elf_compress.c:214
Compiled with: gcc-6.3.0
Reproducer:
https://github.com/asarubbo/poc/blob/master/00227-elfutils-memallocfailure
Stacktrace attached.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-03-24 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 9:20 ago at gentoo dot org [this message]
2017-03-24 13:53 ` [Bug libelf/21301] " mjw at redhat dot com
2017-04-03 21:54 ` mark at klomp dot org
2017-04-10 7:31 ` ago at gentoo 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-21301-10460@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).