From: "wcventure at 126 dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/23752] New: Invalid Address Read problem in dwfl_segment_report_module.c when executing ./eu-stack --core=$POC
Date: Wed, 10 Oct 2018 09:32:00 -0000 [thread overview]
Message-ID: <bug-23752-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=23752
Bug ID: 23752
Summary: Invalid Address Read problem in
dwfl_segment_report_module.c when executing ./eu-stack
--core=$POC
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libdw
Assignee: unassigned at sourceware dot org
Reporter: wcventure at 126 dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Created attachment 11306
--> https://sourceware.org/bugzilla/attachment.cgi?id=11306&action=edit
POC-stack
Hi there,
Our fuzzer caught Invalid Address Read problem in eu-stack of the latest
elfutils-0.174 code base, this inputs will cause the segment faults and I have
confirmed them with address sanitizer too. Please use the "./eu-stack
--core=$POC" or "./eu-stack --core=$POC -abdilmsv" to reproduce the bug. If you
have any questions, please let me know.
The ASAN dumps the stack trace as follows:
ASAN:DEADLYSIGNAL
=================================================================
==9753==ERROR: AddressSanitizer: SEGV on unknown address 0x7f6afb9ac114 (pc
0x7f6afa17a7dc bp 0x7fffc8bb1900 sp 0x7fffc8bb17f0 T0)
==9753==The signal is caused by a READ memory access.
#0 0x7f6afa17a7db in consider_notes
/elfutils-0.174/libdwfl/dwfl_segment_report_module.c:486
#1 0x7f6afa17accc in consider_phdr
/elfutils-0.174/libdwfl/dwfl_segment_report_module.c:529
#2 0x7f6afa176fa2 in dwfl_segment_report_module
/elfutils-0.174/libdwfl/dwfl_segment_report_module.c:590
#3 0x7f6afa185ce0 in dwfl_core_file_report
/elfutils-0.174/libdwfl/core-file.c:541
#4 0x405106 in parse_opt /elfutils-0.174/src/stack.c:590
#5 0x7f6af9a64847 in argp_parse (/lib/x86_64-linux-gnu/libc.so.6+0x114847)
#6 0x4056a7 in main /elfutils-0.174/src/stack.c:690
#7 0x7f6af997082f in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x2082f)
#8 0x402308 in _start (/elfutils-0.174/build/bin/eu-stack+0x402308)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV
/elfutils-0.174/libdwfl/dwfl_segment_report_module.c:486 in consider_notes
==9753==ABORTING
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-10-10 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 9:32 wcventure at 126 dot com [this message]
2018-10-14 13:14 ` [Bug libdw/23752] " mark at klomp dot org
2018-10-14 14:49 ` mark at klomp dot org
2018-10-14 15:03 ` mark at klomp dot org
2018-10-14 16:23 ` wcventure at 126 dot com
2018-10-19 22:27 ` mark at klomp dot org
2018-11-14 11:53 ` 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-23752-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).