dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2026-24182

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to 535.309.01 / 539.72 or later.
See remediation →
67/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 Display Driver for Windows and Linux contains a vulnerability where an attacker could leak held driver locks. A successful exploit of this vulnerability 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 Display Driver for Windows and Linux contains a race condition vulnerability where an attacker can leak held driver locks. When locks are improperly released or leaked in the kernel-mode graphics driver, it can cause resource exhaustion or deadlock conditions, leading to system instability and denial of service.

MitigationApply the vendor-provided security update for the NVIDIA Display Driver. Until patched, monitor for abnormal driver behavior and consider restricting untrusted code execution in the graphics driver context.

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:>= 535, < 535.309.01>= 535, < 539.72>= 580, < 580.159.03>= 580, < 582.53>= 595, < 595.36>= 595, < 595.71.05

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 installed NVIDIA display driver version on Windows
    Open Device Manager, expand 'Display adapters', right-click the NVIDIA GPU, select 'Properties', go to the 'Driver' tab. Alternatively, run 'nvidia-smi' from command line (if available) or check 'Programs and Features' for NVIDIA driver entries.
    Affected if The driver version displayed falls within any of these ranges: 535.x (below 535.309.01 or 539.72), 580.x (below 580.159.03 or 582.53), or 595.x (below 595.36 or 595.71.05)
  2. Identify installed NVIDIA display driver version on Linux
    Run 'nvidia-smi' from terminal and check the 'Driver Version' field. Alternatively, run 'cat /proc/driver/nvidia/version' or check 'dpkg -l | grep nvidia' (Debian/Ubuntu) or 'rpm -qa | grep nvidia' (RHEL/CentOS).
    Affected if The driver version displayed falls within any of these ranges: 535.x (below 535.309.01 or 539.72), 580.x (below 580.159.03 or 582.53), or 595.x (below 595.36 or 595.71.05)
  3. Check for symptoms of lock contention or thread hangs
    On Windows, use Task Manager or Process Explorer to monitor for processes appearing unresponsive, especially NVDisplay.Container.exe or nvidia.exe. On Linux, check 'top' or 'ps' for processes in uninterruptible sleep state (state 'D'). Use 'dmesg' to look for kernel warnings related to NVIDIA driver timeouts.
    Affected if Applications or the desktop becomes unresponsive during graphics operations, threads appear stuck in 'D' state, or kernel logs show NVIDIA driver timeout messages, especially under graphics load.
  4. Verify if local untrusted user access exists
    Review system user accounts and permissions. Check if there are non-admin users or service accounts with local console or RDP access who could potentially trigger the race condition. Audit logged-in users via 'query user' (Windows) or 'who'/'w' (Linux).
    Affected if Local untrusted or low-privilege users have access to log into the system interactively, as the attacker requires local access to trigger the lock leak.

You are affected if your NVIDIA display driver version falls within the vulnerable version ranges AND local untrusted users have system access, combined with observed symptoms of thread hangs or lock contention during graphics operations.

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 535.309.01 / 539.72 / 580.159.03 or later
Fixed in 535.309.01539.72580.159.03
Interim mitigation

Apply the vendor-provided security update for the NVIDIA Display Driver. Until patched, monitor for abnormal driver behavior and consider restricting untrusted code execution in the graphics driver context.

Recommended fix High confidence

535.309.01, 539.72, 580.159.03, or 582.53 (depending on your current driver branch)

  1. 1. Identify your current NVIDIA display driver version by opening NVIDIA Control Panel and checking 'System Information' or by running 'nvidia-smi' in command prompt
  2. 2. Download the appropriate fixed driver version for your GPU series from NVIDIA's official download page (nvidia.com/Download/index.aspx) or use NVIDIA GeForce Experience
  3. 3. For branch 535.x: upgrade to version 535.309.01 or later
  4. 4. For branch 539.x: upgrade to version 539.72 or later
  5. 5. For branch 580.x: upgrade to version 580.159.03 or later
  6. 6. For branch 582.x: upgrade to version 582.53 or later
  7. 7. Uninstall the current display driver completely before installing the new version using the 'Clean Install' option
  8. 8. Reboot the system after installation completes

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

Fix this in Gpu Display Driver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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