[Nasm-bugs] [Bug 3392518] New: Malformed input file leads to invalid read and NASM segmentation fault

[noreply-nasm at gorcunov.org]

https://bugzilla.nasm.us/show_bug.cgi?id=3392518

            Bug ID: 3392518
           Summary: Malformed input file leads to invalid read and NASM
                    segmentation fault
           Product: NASM
           Version: 2.14 (development)
          Hardware: All
                OS: All
            Status: OPEN
          Severity: normal
          Priority: Medium
         Component: Assembler
          Assignee: nobody at nasm.us
          Reporter: j.zebor at f5.com
                CC: gorcunov at gmail.com, hpa at zytor.com, nasm-bugs at nasm.us
     Obtained from: Build from source archive using configure

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

Input of a malformed file to nasm results in a segmentation fault (SIGSEGV).
The problem appears to be an invalid read in "expand_mmac_params_range". I
confirmed this issue on NASM version 2.13.03 and NASM version 2.14rc15 with the
command "nasm -f bin expand_mmac_params_range_crash.asm"

Valgrind report indicates an issue due to "The signal is caused by a READ
memory access. Hint: address points to the zero page.". I'll leave it to the
experts on this to determine specific root cause. Attached is the sample input
file (expand_mmac_params_range_crash.asm) and valgrind log (valgrind.log).

This bug was found with American Fuzzy LOP.

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