dbcve.org
Virtual GpuApplication · Nvidia

CVE-2024-0084

HIGH · 7.8 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 13.11 / 16.6 or later.
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 contains a vulnerability in the Virtual GPU Manager, where the guest OS could execute privileged operations. A successful exploit of this vulnerability might lead to information disclosure, data tampering, escalation of privileges, and 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 confidence

NVIDIA vGPU software for Linux contains a vulnerability in the Virtual GPU Manager where a malicious or compromised guest OS can execute privileged operations that should be restricted to the hypervisor or host level. This represents a virtualization escape/privilege escalation flaw allowing a guest VM to break out of its isolation boundaries.

MitigationApply the latest NVIDIA vGPU software security updates to the Virtual GPU Manager (hypervisor component). Review guest VM access controls and monitor for signs of exploitation until patches are deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Virtual GpuApplication
Affected:< 13.11>= 14.0, < 16.6>= 17.0, < 17.2
Cloud GamingApplication
Affected:< 555.52.04

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. Identify if NVIDIA vGPU software is installed
    On the hypervisor host, check for the presence of vGPU Manager packages or drivers. For Linux, examine installed packages related to 'nvidia-vgpu' or 'vgpu' using package managers (e.g., 'dpkg -l | grep vgpu', 'rpm -qa | grep vgpu'). For Windows hypervisors, check installed programs for NVIDIA vGPU components.
    Affected if No vGPU software is installed, the system is not affected by this vulnerability.
  2. Determine the Virtual GPU Manager version
    On the hypervisor, retrieve the vGPU Manager version. For Linux, this may be available via 'modinfo nvidia_vgpu_vfio' or checking the driver package version. For Windows, check the driver details of the NVIDIA vGPU Manager in Device Manager or via 'nvvgpu' utilities if available. Compare the version number against the affected ranges: < 13.11, >= 14.0 and < 16.6, >= 17.0 and < 17.2 for Virtual GPU; < 555.52.04 for Cloud Gaming.
    Affected if The installed version falls within any of the affected ranges listed.
  3. Verify if guest VMs have vGPU passthrough configured
    On the hypervisor, enumerate guest VMs to identify those with vGPU devices assigned. For VMware, check VM configuration for 'PCI Device' or 'vGPU' assignments. For other hypervisors supporting NVIDIA vGPU, review the VM configuration files or management interface for assigned virtual GPUs.
    Affected if Guest VMs are configured with vGPU passthrough devices and the vGPU Manager version is vulnerable.
  4. Confirm the hypervisor environment type
    Verify that the host system is running a supported hypervisor that utilizes NVIDIA vGPU (e.g., VMware vSphere, Citrix XenServer, Microsoft Azure, or other platforms listed in NVIDIA vGPU compatibility matrices). Check hypervisor version and confirm vGPU support is enabled.
    Affected if The system is a hypervisor with active vGPU functionality and the vGPU Manager version is vulnerable.

A system is affected if it runs a vulnerable version of NVIDIA Virtual GPU Manager or Cloud Gaming (per the version ranges) with guest VMs configured to use vGPU passthrough, allowing a malicious guest to potentially escape virtualization boundaries.

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.

dbcve · scoped
Upgrade available Upgrade to 13.11 / 16.6 / 17.2 or later
Fixed in 13.1116.617.2
Interim mitigation

Apply the latest NVIDIA vGPU software security updates to the Virtual GPU Manager (hypervisor component). Review guest VM access controls and monitor for signs of exploitation until patches are deployed.

Recommended fix Moderate confidence

Virtual GPU: 13.11 (for 13.x branch), 16.6 (for 14.x-16.x branch), or 17.2 (for 17.x branch) | Cloud Gaming: 555.52.04

  1. Identify the currently installed NVIDIA vGPU software version using 'nvidia-smi' or checking the vGPU Manager package version
  2. For Virtual GPU installations: Upgrade to version 13.11 or later (if on 13.x branch), 16.6 or later (if on 14.x-16.x branch), or 17.2 or later (if on 17.x branch)
  3. For Cloud Gaming installations: Upgrade to version 555.52.04 or later
  4. After upgrading, verify the Virtual GPU Manager is running the fixed version by checking the NVIDIA kernel module version
  5. Ensure the guest VM vGPU driver version is compatible with the updated Virtual GPU Manager version
  6. Restart the vGPU-enabled virtual machines if required by the upgrade process
Caveat Review NVIDIA vGPU software release notes for any guest driver compatibility changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Virtual Gpu Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0084 — 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-2024-0084 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