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-23273: CWE-369 Divide By Zero in NVIDIA NVIDIA CUDA Toolkit

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

Description

NVIDIA CUDA Toolkit for all platforms contains a vulnerability in nvJPEG where a local authenticated user may cause a divide by zero error by submitting a specially crafted JPEG file. A successful exploit of this vulnerability may lead to denial of service.

AI-Powered Analysis

AILast updated: 09/24/2025, 13:29:25 UTC

Technical Analysis

CVE-2025-23273 is a vulnerability identified in the NVIDIA CUDA Toolkit, specifically within the nvJPEG component responsible for JPEG image processing. This vulnerability is classified as a CWE-369 Divide By Zero error. It affects all versions of the CUDA Toolkit prior to version 13.0. The flaw arises when a local authenticated user submits a specially crafted JPEG file that triggers a divide by zero operation within the nvJPEG processing code. This results in a denial of service (DoS) condition, causing the affected application or system component to crash or become unresponsive. The vulnerability requires local authentication, meaning the attacker must have some level of access to the system to exploit it. No user interaction beyond submitting the malicious JPEG file is necessary. The CVSS v3.1 base score is 2.5, indicating a low severity primarily due to the limited impact scope (denial of service only), the requirement for local privileges, and the high attack complexity. There are no known exploits in the wild at the time of publication, and no official patches have been linked yet, though upgrading to CUDA Toolkit 13.0 or later is implied as a remediation step. This vulnerability does not impact confidentiality or integrity but affects availability by causing service disruption through a crash or hang triggered by the divide by zero error in image processing.

Potential Impact

For European organizations utilizing NVIDIA CUDA Toolkit in their computing environments—particularly those involved in high-performance computing, AI research, scientific simulations, or image processing workflows—this vulnerability poses a risk of local denial of service. While the impact is limited to availability and does not compromise data confidentiality or integrity, disruption of critical GPU-accelerated workloads could affect operational continuity. Organizations relying on automated image processing pipelines or GPU-accelerated applications that handle JPEG files may experience unexpected crashes or service interruptions if an attacker with local access submits malicious JPEG files. This could lead to downtime, loss of productivity, and potential cascading effects in tightly integrated computational environments. However, the requirement for local authentication and the high complexity of exploitation reduce the likelihood of widespread impact. Nonetheless, environments with shared access or multi-user systems where users have local accounts could be more vulnerable to exploitation attempts.

Mitigation Recommendations

European organizations should implement the following specific mitigation measures: 1) Upgrade to NVIDIA CUDA Toolkit version 13.0 or later as soon as it becomes available, as this version addresses the vulnerability. 2) Restrict local user privileges strictly to minimize the number of users who can execute or submit JPEG files to GPU-accelerated applications using nvJPEG. 3) Implement application-level input validation and sanitization for JPEG files before processing to detect and block malformed or suspicious images that could trigger the divide by zero error. 4) Monitor GPU-accelerated application logs and system stability metrics for signs of crashes or hangs related to image processing. 5) Employ endpoint security solutions that can detect anomalous local user behavior or attempts to exploit local vulnerabilities. 6) In multi-user environments, consider isolating GPU workloads per user or containerizing GPU applications to limit the blast radius of potential DoS attacks. 7) Maintain up-to-date backups and recovery procedures to minimize operational impact in case of service disruption.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 68d3f06c37fc381b138d5304

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

Last enriched: 9/24/2025, 1:29:25 PM

Last updated: 10/7/2025, 1:52:02 PM

Views: 30

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