[Bug binutils/27793] New: [nm] segv in bfd.h:1233

[dkcjd2000 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=27793

            Bug ID: 27793
           Summary: [nm] segv in bfd.h:1233
           Product: binutils
           Version: 2.37 (HEAD)
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: dkcjd2000 at gmail dot com
  Target Milestone: ---

Created attachment 13405
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13405&action=edit
crash test case

Hello,
I report a SEGV detected by address sanitizer.
I found this test input by a fuzz testing.

The stack traces is as follows:
==6834==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000029 (pc
0x000000697f76 bp 0x62a0000007f0 sp 0x7fffffffdc40 T0)
==6834==The signal is caused by a READ memory access.
==6834==Hint: address points to the zero page.
    #0 0x697f76 in bfd_is_com_section
.../subjects/binutils-gdb/bfd/./bfd.h:1233:39
    #1 0x697f76 in som_decode_symclass
.../subjects/binutils-gdb/bfd/som.c:5843:7
    #2 0x697f76 in som_get_symbol_info
.../subjects/binutils-gdb/bfd/som.c:5893:15
    #3 0xe7f43e in print_symbol .../subjects/binutils-gdb/binutils/nm.c:939:3
    #4 0xe7ebe6 in print_symbols .../subjects/binutils-gdb/binutils/nm.c:1152:7
    #5 0xe7ebe6 in display_rel_file
.../subjects/binutils-gdb/binutils/nm.c:1279:5
    #6 0xe7cdde in display_file .../subjects/binutils-gdb/binutils/nm.c:1446:7
    #7 0xe7bfac in main .../subjects/binutils-gdb/binutils/nm.c:1965:12
    #8 0x7ffff6e22bf6 in __libc_start_main
/build/glibc-S9d2JN/glibc-2.27/csu/../csu/libc-start.c:310
    #9 0x5661a9 in _start (.../afl++/subjects_friend/nm/nm.san+0x5661a9)

You can reproduce the bug by executing
./nm -C <test input>

I tested the subject on the latest version uploaded on git,
build with --disable-shared --disable-gdb --disable-libdecnumber --disable-ld
--enable-targets=all
configure options.

Thanks

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