[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/28055] New: Segment fault on nm-new -l

From: shaohua.li at inf dot ethz.ch
Subject: [Bug binutils/28055] New: Segment fault on nm-new -l
Date: Sun, 04 Jul 2021 22:13:03 +0000


            Bug ID: 28055
           Summary: Segment fault on nm-new -l
           Product: binutils
           Version: 2.38 (HEAD)
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: shaohua.li at inf dot ethz.ch
  Target Milestone: ---

Created attachment 13536
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13536&action=edit

Hi there,

I crashed `nm-new -l` with a fuzzer.

- Compiler: clang12
- Platform: Ubuntu 18.04.5 LTS, x86_64
- Reproduce: run `nm-new -l poc`

AddressSanitizer report:

==8695==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc
0x00000097d395 bp 0x000000000008 sp 0x7ffd8e175e40 T0)
==8695==The signal is caused by a READ memory access.
==8695==Hint: address points to the zero page.
    #0 0x97d395 in bpf_elf_generic_reloc
    #1 0x10414f8 in bfd_perform_relocation
    #2 0x1044646 in bfd_generic_get_relocated_section_contents
    #3 0x1045a35 in bfd_simple_get_relocated_section_contents
    #4 0x62f126 in read_section
    #5 0x62c867 in _bfd_dwarf2_slurp_debug_info
    #6 0x635cdd in _bfd_dwarf2_find_nearest_line
    #7 0x59692a in _bfd_elf_find_line
    #8 0x4cea5a in print_symbol
    #9 0x4ccfed in print_symbols
    #10 0x4ccfed in display_rel_file
    #11 0x4c94ea in display_file
    #12 0x4c8add in main //shared/targets/nm-new/repo/binutils/nm.c:1965:12
    #13 0x7f07677b5bf6 in __libc_start_main
    #14 0x41c149 in _start (/out_bin/nm-new+0x41c149)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV
//shared/targets/nm-new/repo/bfd/elf64-bpf.c:651:7 in bpf_elf_generic_reloc

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]