dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2024-0092

MEDIUM · 5.5 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 13.11 / 16.6 or later.
See remediation →
57/100
Remediation priority · Elevated
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 Driver for Windows and Linux contains a vulnerability where an improper check or improper handling of exception conditions 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 confidence

NVIDIA GPU Driver for Windows and Linux contains a vulnerability where an improper check or improper handling of exception conditions might lead to denial of service. The issue allows a local attacker to potentially cause a denial of service through improper error handling in the GPU driver.

MitigationApply the latest NVIDIA GPU driver update when available. Monitor NVIDIA Security Bulletins for patch release.

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>= 470, < 470.256.02>= 535, < 535.180.01>= 550, < 550.90.07>= 555, < 555.52.04
Virtual GpuApplication
Affected:< 13.11>= 14.0, < 16.6>= 17.0, < 17.2< 17.2
Cloud GamingApplication
Affected:all versions< 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
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 checks

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

  1. Identify NVIDIA driver product type
    Determine whether the system uses NVIDIA GPU Display Driver, NVIDIA Virtual GPU (vGPU), or NVIDIA Cloud Gaming. For display drivers, run 'nvidia-smi' or check Windows Device Manager. For vGPU, check the hypervisor or guest VM configuration. For Cloud Gaming, identify if NVIDIA Gaming or GeForce NOW infrastructure is in use.
    Affected if Any of these three product types are in use
  2. Check GPU Display Driver version (Windows/Linux)
    Run 'nvidia-smi' and note the Driver Version field (e.g., 535.154.05). On Windows, also check the Display Adapter properties in Device Manager for the driver version. For Linux, check /proc/driver/nvidia/version or run 'nvcc --version' if installed.
    Affected if Driver version is 470.x.x to 474.x.x, 475.00 to 475.05; 535.x.x to 538.66; 550.x.x to 552.54; 555.x.x to 555.98; 470.0 to 470.256.01; 535.0 to 535.180.00; 550.0 to 550.90.06; 555.0 to 555.52.03
  3. Check Virtual GPU (vGPU) software version
    On the hypervisor (VMware ESXi, Citrix XenServer, or KVM), run 'nvidia-smi' or check the vGPU Manager version. In the guest VM, run 'nvidia-smi' to see the vGPU driver version provided by the hypervisor.
    Affected if vGPU software version is below 13.11, or between 14.0 and 16.5, or between 17.0 and 17.1, or below 17.2
  4. Check NVIDIA Cloud Gaming version
    Identify if the system runs NVIDIA Cloud Gaming or GeForce NOW server software. Check the installed NVIDIA Cloud Gaming software version through the application or service management interface.
    Affected if Any version of NVIDIA Cloud Gaming is installed, or version is below 555.52.04

The environment is affected if any NVIDIA GPU driver, vGPU software, or Cloud Gaming version matches the affected version ranges listed above.

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 GPU driver update when available. Monitor NVIDIA Security Bulletins for patch release.

Recommended fix High confidence

GPU Display Driver: 475.06 (470 series), 538.67 (535 series), 552.55 (550 series), or 555.99 (555 series) | vGPU: 13.11, 16.6, or 17.2 depending on branch | Cloud Gaming: 555.52.04

  1. 1. Identify the current NVIDIA driver version by running 'nvidia-smi' on Linux or checking 'Programs and Features' > 'NVIDIA' on Windows
  2. 2. Determine which driver branch (470, 535, 550, or 555 series) is currently installed
  3. 3. Download the fixed driver version from NVIDIA's official website (nvidia.com) or NVIDIA's support portal matching your branch: 475.06 (for 470.xx), 538.67 (for 535.xx), 552.55 (for 550.xx), or 555.99 (for 555.xx)
  4. 4. For Virtual GPU users: upgrade to version 13.11, 16.6, or 17.2 depending on the installed branch
  5. 5. For Cloud Gaming users: upgrade to version 555.52.04
  6. 6. Install the new driver package following NVIDIA's standard installation procedure
  7. 7. Reboot the system after installation completes
Caveat Standard NVIDIA driver upgrade - no major breaking changes expected; however, ensure compatibility with your GPU model and verify application compatibility 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
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,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 $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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