Local crash via freed directive structure
Published Aug 11, 2025 · Updated Aug 11, 2025
Use-after-free in NASM 2.17rc0 allows local users to crash the assembler by processing a malformed file with crafted preprocessor directives. The do_directive path reads four bytes from a directive structure after pp_tokline frees its 192-byte allocation during token processing. Triggering requires low-privileged local execution with the crafted file; the demonstrated consequence is an assembler-process abort, not a system-wide service interruption.
Summary
What happened
Use-after-free in NASM 2.17rc0 allows local users to crash the assembler by processing a malformed file with crafted preprocessor directives. The do_directive path reads four bytes from a directive structure after pp_tokline frees its 192-byte allocation during token processing. Triggering requires low-privileged local execution with the crafted file; the demonstrated consequence is an assembler-process abort, not a system-wide service interruption.
The record
- CVE
- CVE-2025-8842
- Published
- Aug 11, 2025
- Updated
- Aug 11, 2025
- Vendor
- NASM
- Product
- NASM
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.17rc0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- POC_nasm_use_after_free_do_directiveproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo