CVE-2025-23285
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager, where it allows a guest to access global resources. A successful exploit of this vulnerability might lead to denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceNVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager where a guest virtual machine can improperly access global resources that should be isolated between virtual machines. This improper resource access can lead to denial of service conditions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify NVIDIA vGPU software is installedOn the hypervisor host, check for the presence of NVIDIA vGPU Manager. For VMware ESXi, run 'esxcli software vib list | grep -i nvidia'. For other hypervisors, check the installed packages or services related to vGPU.Affected if NVIDIA vGPU Manager is installed on the host system
-
Determine the Virtual GPU Manager versionRetrieve the installed vGPU Manager version. For VMware ESXi, use 'esxcli software vib list | grep -i vgpu' or check the VIB package version. Note the full version string including build number.Affected if The installed version matches or falls within the affected version range (compare to NVIDIA's official advisory)
-
Confirm vGPU functionality is enabledCheck if any guest virtual machines are configured with vGPU devices. For VMware, examine the VM configuration for 'pciPassthru' assignments or review the vGPU profile assignments via 'nvidia-smi vgpu -l' or hypervisor-specific vGPU management tools.Affected if Guest VMs have vGPU devices assigned and are actively using vGPU resources
-
Check for resource isolation issuesMonitor guest VMs for unexpected behavior indicating resource contention, such as sudden performance degradation, GPU errors in system logs, or VMs accessing resources belonging to other vGPU-enabled VMs. Review hypervisor logs for vGPU-related errors or warnings.Affected if Guest VMs exhibit denial of service symptoms or resource access anomalies
A system is affected if NVIDIA Virtual GPU Manager is installed with a version within the affected range AND guest VMs are configured with vGPU devices, allowing potential cross-VM resource access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the latest NVIDIA vGPU software updates when available. Until a patch is released, monitor for unusual guest VM behavior and ensure proper isolation configurations are in place.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23285 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23285 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data