dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2024-0089

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 GPU Display Driver for Windows contains a vulnerability where the information from a previous client or another process could be disclosed. A successful exploit of this vulnerability might lead to code execution, 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 · moderate confidence

NVIDIA GPU Display Driver for Windows contains a vulnerability where information from a previous client or another process could be disclosed. This improper data isolation in the display driver could allow a local attacker to access residual data in memory, potentially leading to code execution, information disclosure, or data tampering.

MitigationApply the NVIDIA driver update or patch released to address this vulnerability. Verify that affected systems receive the updated driver and confirm the remediation through testing.

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
Gpu Display DriverApplication
Affected:>= 470, < 475.06>= 535, < 538.67>= 550, < 552.55>= 555, < 555.99
Virtual GpuApplication
Affected:< 13.11>= 14.0, < 16.6>= 17.0, < 17.2
Cloud GamingApplication
Affected:< 555.99

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. Check NVIDIA GPU driver version on Windows
    Open Command Prompt or PowerShell and run 'nvidia-smi' to display driver version, or open Device Manager, expand 'Display adapters', right-click the NVIDIA GPU, select Properties, and view the Driver Version field
    Affected if The displayed driver version falls within one of these ranges: 470.x to 475.05, 535.x to 538.66, 550.x to 552.54, or 555.x to 555.98
  2. Check driver version via Windows Registry
    Open Registry Editor (regedit), navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\Device0, and inspect the DriverVersion value
    Affected if The DriverVersion value matches any of the affected version ranges listed above
  3. Check NVIDIA vGPU Manager version for virtual environments
    For systems running NVIDIA Virtual GPU, check the vGPU Manager version via Hyper-V or VMware hypervisor console, or run 'nvidia-smi' in the management VM to view the vGPU software version
    Affected if The vGPU Manager version is below 13.11, or between 14.0 and 16.5, or between 17.0 and 17.1
  4. Check NVIDIA Cloud Gaming installation version
    Open the NVIDIA GeForce NOW or Cloud Gaming application, navigate to Settings or About, and note the software version
    Affected if The Cloud Gaming client version is below 555.99

A system is affected if the installed NVIDIA driver, vGPU Manager, or Cloud Gaming client version falls within any of the specific version ranges listed as affected for this CVE.

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 NVIDIA driver update or patch released to address this vulnerability. Verify that affected systems receive the updated driver and confirm the remediation through testing.

Recommended fix High confidence

Gpu Display Driver: 475.06, 538.67, 552.55, or 555.99; Virtual Gpu: 13.11, 16.6, or 17.2; Cloud Gaming: 555.99

  1. Identify your current NVIDIA GPU driver version via nvidia-smi or Device Manager
  2. Download the appropriate fixed driver version from nvidia.com/drivers or your enterprise deployment tools
  3. Uninstall the current GPU display driver completely before installing the new version
  4. Install the fixed version corresponding to your product line: Display Driver >= 475.06 (for 470.x series), >= 538.67 (for 535.x series), >= 552.55 (for 550.x series), or >= 555.99 (for 555.x series); Virtual GPU >= 13.11, >= 16.6, or >= 17.2; Cloud Gaming >= 555.99
  5. Restart the system to ensure the new driver loads properly
  6. Verify the installed version matches the expected fixed release
Caveat Driver updates may affect application compatibility; test in staging before production deployment

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

Fix this in Gpu Display Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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