# CVE-2025-23274: Integer overflow in NVIDIA CUDA Toolkit

> An attacker can cause a denial of service in NVIDIA nvJPEG by providing a malicious image that triggers integer overflows and out-of-bounds reads.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** DEBIAN-CVE-2025-23274, GHSA-wgw9-m369-f899, UBUNTU-CVE-2025-23274

## What is CVE-2025-23274?

CVE-2025-23274 is a medium-severity vulnerability in NVIDIA CUDA Toolkit, published on 24 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA nvJPEG contains a vulnerability in jpeg encoding where a user may cause an out-of-bounds read by providing a maliciously crafted input image with dimensions that cause integer overflows in array index calculations. A successful exploit of this vulnerability may lead to denial of service.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-23274?


## How do I fix CVE-2025-23274?

No fix has been published for CVE-2025-23274 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-23274 being exploited?

There is no known exploitation of CVE-2025-23274 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23274 and fix it if it is affected.

What it is: CVE-2025-23274 is a medium-severity vulnerability in NVIDIA CUDA Toolkit, published on 24 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23274 in the wild and no public exploit code.

Affected product: NVIDIA CUDA Toolkit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-23274/ (Markdown: https://insights.sbomify.com/CVE-2025-23274/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23274
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23274
- OSV: https://osv.dev/vulnerability/CVE-2025-23274

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-23274/
Summaries are generated and may contain mistakes; the official description above is the record.