Tool interruption via malformed REL section size
Published Sep 24, 2025 · Updated Sep 24, 2025
Out-of-bounds read in NVIDIA CUDA Toolkit nvdisasm before 13.0 allows local users to interrupt the tool by opening a malformed ELF file. In REL section parsing, incompatible allocation and loop sizes derived from sh_size drive memory access beyond a heap buffer. Execution requires a user to run nvdisasm on the file; NVIDIA reports partial denial of service, while Cisco Talos reports controlled heap corruption and code execution.
Summary
What happened
Out-of-bounds read in NVIDIA CUDA Toolkit nvdisasm before 13.0 allows local users to interrupt the tool by opening a malformed ELF file. In REL section parsing, incompatible allocation and loop sizes derived from sh_size drive memory access beyond a heap buffer. Execution requires a user to run nvdisasm on the file; NVIDIA reports partial denial of service, while Cisco Talos reports controlled heap corruption and code execution.
The record
- CVE
- CVE-2025-23271
- Published
- Sep 24, 2025
- Updated
- Sep 24, 2025
- Vendor
- DPDK Project
- Product
- CUDA Toolkit
- Classifications
- CWE-122, CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 24, 2025CVE publishedPublication date reported by the CVE source.
- Sep 24, 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=All versions prior to CUDA Toolkit 13.0
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
No public exploit references are available in this record.
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