CVE-2025-23248VulnerabilityPublished 24 Sep 2025

CVE-2025-23248: NVIDIA CUDA Toolkit · Out-of-bounds Read

Affects NVIDIA CUDA ToolkitSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low : upgrade to 13.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 13.0

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade NVIDIA CUDA Toolkit to 13.0.

Affected software

Product	Affected	Fixed in
NVIDIA NVIDIA CUDA Toolkit	Affected <13.0	Fixed in 13.0

AI-suggested

To mitigate CVE-2025-23248, European organizations should: 1) Upgrade to NVIDIA CUDA Toolkit version 13.0 or later, where this vulnerability is addressed. 2) Restrict local access to systems running the CUDA Toolkit and the nvdisasm tool to trusted users only, enforcing strict access controls and user account management. 3) Implement endpoint protection and monitoring to detect unusual activity related to ELF file handling or nvdisasm execution. 4) Educate users about the risks of opening untrusted or malformed ELF files, especially in development environments. 5) Use sandboxing or containerization for tools like nvdisasm to limit the impact of potential crashes or denial of service conditions. 6) Regularly audit and update GPU driver and toolkit software to ensure all security patches are applied promptly. 7) Incorporate file integrity monitoring for critical binaries and scripts to detect unauthorized modifications or suspicious files.

Description

NVIDIA CUDA Toolkit for all platforms contains a vulnerability in the nvdisasm binary where a user may cause an out-of-bounds read by passing a malformed ELF file to nvdisasm. A successful exploit of this vulnerability may lead to a partial denial of service.

Impact

For European organizations, the impact of CVE-2025-23248 is generally limited due to the low severity and the requirement for local access and user interaction. However, organizations heavily reliant on NVIDIA CUDA Toolkit for GPU-accelerated computing, such as research institutions, high-performance computing centers, AI and machine learning companies, and industries using GPU-based simulations, could experience disruptions if the nvdisasm tool is exploited to cause denial of service. While the vulnerability does not compromise confidentiality or integrity, a denial of service could interrupt critical development workflows or automated analysis pipelines, potentially delaying project timelines or impacting operational efficiency. The risk is mitigated by the need for an attacker to have local access and to convince a user to open a malicious ELF file, which reduces the likelihood of remote exploitation. Nonetheless, insider threats or compromised local accounts could leverage this vulnerability to disrupt services. Given the increasing adoption of GPU computing in Europe, especially in technology hubs and research centers, awareness and timely patching are important to maintain operational stability.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Sep 2025, 13:22 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats