# CVE-2025-23352: Null dereference in Virtual GPU Manager

> A malicious guest can exploit uninitialized pointer access in NVIDIA vGPU Manager to execute code, escalate privileges, or cause denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 23 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-86xc-5www-fwxw

## What is CVE-2025-23352?

CVE-2025-23352 is a high-severity vulnerability in NVIDIA Virtual GPU Manager, published on 23 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager, where a malicious guest could cause uninitialized pointer access. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.

Weakness: CWE-824 (Access of Uninitialized Pointer)

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


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

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

## Is CVE-2025-23352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23352 is a high-severity vulnerability in NVIDIA Virtual GPU Manager, published on 23 Oct 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-23352 in the wild and no public exploit code.

Affected product: NVIDIA Virtual GPU Manager. 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-23352/ (Markdown: https://insights.sbomify.com/CVE-2025-23352/index.md)
```

## Sources

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

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