# CVE-2025-23246: Denial of service in vGPU Software, Cloud Gaming

> A guest can consume uncontrolled resources in the vGPU plugin, causing a denial of service for the host system.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 1 May 2025
- **Updated:** 1 May 2025
- **Also known as:** GHSA-6cv8-8h5r-cc95

## What is CVE-2025-23246?

CVE-2025-23246 is a medium-severity denial of service vulnerability in NVIDIA vGPU Software, Cloud Gaming, published on 1 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA vGPU software for Windows and Linux contains a vulnerability in the Virtual GPU Manager (vGPU plugin), where it allows a guest to consume uncontrolled resources. A successful exploit of this vulnerability might lead to denial of service.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2025-23246 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23246 is a medium-severity denial of service vulnerability in NVIDIA vGPU Software, Cloud Gaming, published on 1 May 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-23246 in the wild and no public exploit code.

Affected product: NVIDIA vGPU Software, Cloud Gaming. 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-23246/ (Markdown: https://insights.sbomify.com/CVE-2025-23246/index.md)
```

## Sources

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

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