[Nasm-bugs] [Bug 3392845] New: Segmentation Violation in nasm (function set_warning_status)

noreply-nasm at dev.nasm.us noreply-nasm at dev.nasm.us
Thu Mar 16 01:17:41 PDT 2023


            Bug ID: 3392845
           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


Using fuzzer, we found SEGV at 0x2b. It is raised from function
set_warning_status and it seems a corner case of processing command-line

Command Input:
nasm "-w*error"

Sanitizer Dump:
==23188==ERROR: AddressSanitizer: SEGV on unknown address 0x00000000002b (pc
0x555555690f0b bp 0x7fffffffde60 sp 0x7fffffffde30 T0)
==23188==The signal is caused by a READ memory access.
==23188==Hint: address points to the zero page.
    #0 0x555555690f0a in set_warning_status asm/error.c:273
    #1 0x555555683b0f in process_arg asm/nasm.c:1167
    #2 0x555555685668 in parse_cmdline asm/nasm.c:1516
    #3 0x5555556818ed in main asm/nasm.c:583
    #4 0x7ffff6a48c86 in __libc_start_main
    #5 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.

Thank you.

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

More information about the Nasm-bugs mailing list