dbcve.org
Virtual GpuApplication · Nvidia

CVE-2024-0085

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 Windows and Linux contains a vulnerability where unprivileged users could execute privileged operations on the host. A successful exploit of this vulnerability might lead to 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 contains a privilege escalation vulnerability where unprivileged users within virtual machines can execute privileged operations on the host system, potentially breaking the VM-hypervisor isolation boundary.

MitigationApply NVIDIA's patch for vGPU software when released. Restrict vGPU access to trusted, privileged users only until patch is applied.

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< 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 NVIDIA vGPU manager driver. On Linux, look for files in /usr/src/ or check NVIDIA driver packages. On Windows, check Program Files for NVIDIA vGPU components.
    Affected if NVIDIA vGPU software is present on the system
  2. Determine installed vGPU software version
    Run 'nvidia-smi' or check the vGPU manager package version. On Linux: 'rpm -qa | grep vgpu' or 'dpkg -l | grep vgpu'. On Windows, check the installed version in Programs and Features.
    Affected if Installed version is < 13.11, OR >= 14.0 and < 16.6, OR >= 17.0 and < 17.2
  3. Verify vGPU functionality is enabled
    Check if any VMs are configured with vGPU devices. On hypervisor, list active vGPU assignments. For VMware: 'vmware -v' or check vCenter for vGPU-backed VMs. For Citrix: check XenCenter. For KVM: check libvirt domain XML for vGPU device assignment.
    Affected if vGPU-backed virtual machines exist and are running
  4. Identify if NVIDIA Cloud Gaming is installed
    On the gaming server, check for NVIDIA Cloud Gaming software installation. Look for 'NVIDIA GeForce NOW' or similar cloud gaming components. Check installed programs and services.
    Affected if NVIDIA Cloud Gaming software is present and version < 555.52.04

The environment is affected if NVIDIA vGPU or NVIDIA Cloud Gaming is installed with a version falling within the vulnerable ranges and the vGPU functionality is actively in use.

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 NVIDIA's patch for vGPU software when released. Restrict vGPU access to trusted, privileged users only until patch is applied.

Recommended fix Moderate confidence

NVIDIA vGPU: 13.11 (or later), 16.6 (or later), or 17.2 (or later) | NVIDIA Cloud Gaming: 555.52.04 (or later)

  1. Identify the currently installed NVIDIA vGPU or Cloud Gaming software version using nvidia-smi or the vGPU Manager
  2. Based on the installed version branch, upgrade to the first fixed release: For 13.x branch, upgrade to version 13.11 or later; For 14.x-16.x branch, upgrade to version 16.6 or later; For 17.x branch, upgrade to version 17.2 or later; For Cloud Gaming, upgrade to version 555.52.04 or later
  3. Download the appropriate fixed release from the NVIDIA vGPU software downloads page or NVIDIA Enterprise Support portal
  4. Follow NVIDIA's standard vGPU software installation procedure for the guest VM and hypervisor host
  5. After upgrade, verify that unprivileged users can no longer execute privileged operations on the host
Caveat Review NVIDIA vGPU release notes for the target version to check for any configuration or feature changes that may require adjustment

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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