CVE-2025-23273

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.

Published: 2025-09-24 Last update: 2025-10-06 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-23273 is rated Low Risk (10.4/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.01%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-23273

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-09-25 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-23273

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.5 3.1 LOW
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.0 1.4 [email protected]
4.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 3.6 [email protected]

Weakness enumeration for CVE-2025-23273

OS Trackers for CVE-2025-23273

vendor priority summary link
debian not yet assigned CVE-2025-23273 not yet assigned priority: Debian including 1 source packages (nvidia-cuda-toolkit), 4 status rows across 4 suites (bookworm, bullseye, sid, trixie): open 4. https://security-tracker.debian.org/tracker/CVE-2025-23273
ubuntu medium CVE-2025-23273 medium priority: Ubuntu including 1 source packages (nvidia-cuda-toolkit), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): needs-triage 7, ignored 1. https://ubuntu.com/security/CVE-2025-23273

Affected software / configurations for CVE-2025-23273

Vendor Product Version Raw CPE
nvidia cuda_toolkit < 13.0.0 cpe:2.3:a:nvidia:cuda_toolkit:*:*:*:*:*:*:*:*
nvidia nvjpeg — cpe:2.3:a:nvidia:nvjpeg:-:*:*:*:*:*:*:*

References for CVE-2025-23273

cvelogic Threat Intelligence