From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89547 invoked by alias); 10 Oct 2018 09:32:13 -0000 Mailing-List: contact elfutils-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: elfutils-devel-owner@sourceware.org Received: (qmail 88707 invoked by uid 48); 10 Oct 2018 09:31:53 -0000 From: "wcventure at 126 dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: elfutils X-Bugzilla-Component: libdw X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wcventure at 126 dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2018-q4/txt/msg00005.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D23752 Bug ID: 23752 Summary: Invalid Address Read problem in dwfl_segment_report_module.c when executing ./eu-stack --core=3D$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=3D11306&action=3Ded= it 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 h= ave confirmed them with address sanitizer too. Please use the "./eu-stack --core=3D$POC" or "./eu-stack --core=3D$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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D9753=3D=3DERROR: AddressSanitizer: SEGV on unknown address 0x7f6afb9a= c114 (pc 0x7f6afa17a7dc bp 0x7fffc8bb1900 sp 0x7fffc8bb17f0 T0) =3D=3D9753=3D=3DThe 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+0x1148= 47) #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 =3D=3D9753=3D=3DABORTING --=20 You are receiving this mail because: You are on the CC list for the bug.