Assembler crash via NULL pointer dereference
Published May 29, 2025 · Updated May 29, 2025
NULL pointer dereference in Yasm commit 9defefae allows attackers to crash the assembler via a crafted source file. While the NASM parser appends bytecode, yasm_section_bcs_append dereferences a null pointer at section.c line 634, causing a zero-page read. A crafted file must be passed to the local CLI; Debian classifies the result as a crash without security impact.
Summary
What happened
NULL pointer dereference in Yasm commit 9defefae allows attackers to crash the assembler via a crafted source file. While the NASM parser appends bytecode, yasm_section_bcs_append dereferences a null pointer at section.c line 634, causing a zero-page read. A crafted file must be passed to the local CLI; Debian classifies the result as a crash without security impact.
The record
- CVE
- CVE-2024-22653
- Published
- May 29, 2025
- Updated
- May 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 29, 2025CVE publishedPublication date reported by the CVE source.
- May 29, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- Yasm crafted-input proof of conceptproof 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