dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2025-23283

HIGH · 7.8 CVSS v3.1 Published 2025-08-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
NVIDIA vGPU software for Linux-style hypervisors contains a vulnerability in the Virtual GPU Manager, where a malicious guest could cause stack buffer overflow. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, or data tampering.

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 · high confidence

NVIDIA vGPU Manager for Linux-style hypervisors contains a stack buffer overflow vulnerability that can be exploited by a malicious guest VM. Successful exploitation could allow the guest to achieve code execution, denial of service, privilege escalation, information disclosure, or data tampering on the hypervisor host.

MitigationApply NVIDIA's security patch for this vulnerability to the Virtual GPU Manager software. Coordinate a maintenance window to update the hypervisor's vGPU components and verify guest VM functionality post-patch.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm NVIDIA vGPU Manager is installed
    Check for the presence of the vGPU Manager package on the hypervisor. On RHEL/CentOS: rpm -qa | grep -i vgpu. On Ubuntu: dpkg -l | grep -i vgpu. Also check /usr/sbin/nvidia-vgpud or /usr/bin/nvidia-smi for vGPU daemon processes.
    Affected if No NVIDIA vGPU software is installed, the system is not vulnerable to this specific flaw.
  2. Identify the vGPU Manager version
    Run 'nvidia-smi -q' or check the installed RPM/DEB package version: rpm -q nvidia-vgpu-manager or dpkg -l nvidia-vgpu-manager. The version string typically follows the format like 16.x, 17.x, etc.
    Affected if Unable to determine the installed version, assume potential exposure and investigate further.
  3. Verify vGPU functionality is enabled
    Check if any guest VMs are configured with vGPU passthrough. On KVM: virsh list --all and inspect VM XML configs for <hostdev> entries with mdev or vgpu type. Look for nvidia vGPU device assignments.
    Affected if vGPU passthrough is not configured for any VMs, the malicious guest VM attack vector does not apply.
  4. Check for exposed vGPU mdev devices
    List available mdev (mediated devices) types: ls /sys/class/mdev_bus/. Also check /sys/bus/mdev/devices/ for active mdev instances of nvidia types. Use 'cat /sys/class/mdev_bus/*/mdev_supported_types/*/name' to enumerate vGPU types.
    Affected if No nvidia-licensed mdev devices are created or available to guest VMs, the exploit surface is not present.
  5. Compare against fixed version
    NVIDIA typically releases fixes in numbered versions. Document the current installed version from step 2. Cross-reference with NVIDIA's official security bulletin for CVE-2025-23283 to identify the patched version number.
    Affected if The installed version is older than the patched version listed in NVIDIA's security advisory for this CVE.

A system is affected if it runs NVIDIA vGPU Manager with vGPU devices exposed to guest VMs, and the installed version is older than the patched version specified in NVIDIA's CVE-2025-23283 advisory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply NVIDIA's security patch for this vulnerability to the Virtual GPU Manager software. Coordinate a maintenance window to update the hypervisor's vGPU components and verify guest VM functionality post-patch.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23283 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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