Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-23248: CWE-125 Out-of-bounds Read in NVIDIA NVIDIA CUDA Toolkit

0
Low
VulnerabilityCVE-2025-23248cvecve-2025-23248cwe-125
Published: Wed Sep 24 2025 (09/24/2025, 13:11:00 UTC)
Source: CVE Database V5
Vendor/Project: NVIDIA
Product: NVIDIA CUDA Toolkit

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.

AI-Powered Analysis

AILast updated: 09/24/2025, 13:22:17 UTC

Technical Analysis

CVE-2025-23248 is a security vulnerability identified in the NVIDIA CUDA Toolkit, specifically affecting the nvdisasm binary component. The vulnerability is classified as a CWE-125: Out-of-bounds Read. This occurs when the nvdisasm tool processes a malformed ELF (Executable and Linkable Format) file, leading to an out-of-bounds read condition. Such a flaw arises when the program reads data beyond the boundaries of allocated memory buffers, which can cause undefined behavior. In this case, the primary consequence is a partial denial of service (DoS), where the nvdisasm process may crash or become unresponsive. The vulnerability affects all versions of the NVIDIA CUDA Toolkit prior to version 13.0. The CVSS v3.1 base score is 3.3, indicating a low severity level. The vector string (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L) shows that the attack requires local access (AV:L), low attack complexity (AC:L), no privileges (PR:N), but does require user interaction (UI:R). The scope remains unchanged (S:U), and the impact is limited to availability (A:L) with no confidentiality or integrity impact. No known exploits are currently reported in the wild, and no patches are explicitly linked in the provided data, though upgrading to CUDA Toolkit 13.0 or later is implied as a remediation step. The vulnerability is relevant to environments where the nvdisasm tool is used to disassemble CUDA binaries, typically in development, debugging, or reverse engineering contexts involving NVIDIA GPU-accelerated applications.

Potential 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.

Mitigation Recommendations

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.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
nvidia
Date Reserved
2025-01-14T01:06:19.964Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68d3f06c37fc381b138d52eb

Added to database: 9/24/2025, 1:21:48 PM

Last enriched: 9/24/2025, 1:22:17 PM

Last updated: 10/7/2025, 1:51:46 PM

Views: 15

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats