[Nasm-bugs] [Bug 3392848] New: Segmentation Violation in nasm (function obj_write_file)

noreply-nasm at dev.nasm.us noreply-nasm at dev.nasm.us
Thu Mar 16 01:25:38 PDT 2023


            Bug ID: 3392848
           Summary: Segmentation Violation in nasm (function
           Product: NASM
           Version: 2.17 (development)
          Hardware: All
                OS: Linux
            Status: OPEN
          Severity: normal
          Priority: Medium
         Component: Assembler
          Assignee: nobody at nasm.us
          Reporter: youngseok.main at gmail.com
                CC: chang.seok.bae at intel.com, gorcunov at gmail.com,
                    hpa at zytor.com, nasm-bugs at nasm.us
     Obtained from: Built from git using configure

Created attachment 411872
  --> https://bugzilla.nasm.us/attachment.cgi?id=411872&action=edit

Hello, nasm developers.

Our fuzzer found a SEGV bug in nasm.

Command Input:
nasm poc_file -g -f obj

poc_file is attached.

poc_file:1: warning: label alone on a line without a colon might be in error
poc_file:2: warning: no operand for data declaration [-w+db-empty]
poc_file: error: entry point is not in this module

Stack Trace:
==30800==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000018 (pc
0x555555715365 bp 0x7fffffffdfc0 sp 0x7fffffffdf30 T0)
==30800==The signal is caused by a READ memory access.
==30800==Hint: address points to the zero page.
    #0 0x555555715364 in obj_write_file output/outobj.c:2360
    #1 0x55555570b181 in obj_cleanup output/outobj.c:675
    #2 0x555555681f92 in main asm/nasm.c:719
    #3 0x7ffff6a48c86 in __libc_start_main
    #4 0x55555567f699 in _start

OS: Ubuntu 18.04
gcc: 7.5.0
nasm: 2.17rc0 (Git master branch, a916e4127b2eaa3bf40bddf3de9b0ceefc0d98a)

Note that we built nasm with sanitizers.

Any comments related to the crash are welcome. Since we are developing a new
fuzzing technique, it would be very helpful for our work.

Thank you.

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

More information about the Nasm-bugs mailing list