dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2026-24193

HIGH · 7.8 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to 535.309.01 / 539.72 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 Display Driver for Windows and Linux contains a vulnerability where an attacker could cause an out-of-bounds write. A successful exploit of this vulnerability might lead to denial of service, escalation of privileges, information disclosure, data tampering, and code execution.

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 an out-of-bounds write vulnerability that could allow an attacker to corrupt memory beyond allocated buffer boundaries. Successful exploitation may result in denial of service, privilege escalation, information disclosure, data tampering, or arbitrary code execution.

MitigationApply NVIDIA driver updates when released; until patched, minimize exposure by restricting driver access and monitoring for suspicious activity.

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
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 NVIDIA driver version on Windows
    Open Command Prompt and run: nvidia-smi --query-gpu=driver_version --format=csv,noheader. Alternatively, open Control Panel > Programs and Features and look for NVIDIA Display Driver entry to see the installed version number.
    Affected if The displayed version falls within these ranges: 535.x versions before 535.309.01 or before 539.72; 580.x versions before 580.159.03 or before 582.53; 595.x versions before 595.36 or before 595.71.05
  2. Identify NVIDIA driver version on Linux
    Open terminal and run: nvidia-smi --query-gui=driver_version --format=csv,noheader. Or check the installed package version using: dpkg -l | grep nvidia-driver (Debian/Ubuntu) or rpm -qa | grep nvidia-driver (RHEL/CentOS).
    Affected if The displayed version falls within these ranges: 535.x versions before 535.309.01 or before 539.72; 580.x versions before 580.159.03 or before 582.53; 595.x versions before 595.36 or before 595.71.05
  3. Confirm NVIDIA kernel driver is loaded
    Run: lsmod | grep nvidia on Linux or check Device Manager on Windows under Display Adapters to confirm an NVIDIA GPU with installed driver is present.
    Affected if An NVIDIA GPU with a display driver is present and the driver version matches any of the vulnerable version ranges identified in step 1 or 2.

You are affected if an NVIDIA GPU display driver is installed and its version number falls within any of these vulnerable ranges: 535.x before 535.309.01 or 539.72; 580.x before 580.159.03 or 582.53; 595.x before 595.36 or 595.71.05.

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 NVIDIA driver updates when released; until patched, minimize exposure by restricting driver access and monitoring for suspicious activity.

Recommended fix High confidence

535.309.01 (for 535.x branch); 539.72 (for 539.x branch); 580.159.03 (for 580.x branch); 582.53 (for 582.x branch)

  1. Identify the currently installed NVIDIA display driver version by opening NVIDIA Control Panel or running 'nvidia-smi' in command prompt
  2. Determine which branch (535, 539, 580, or 582) your current driver version belongs to
  3. Download the appropriate fixed driver version from the official NVIDIA website (nvidia.com) or your system vendor's support page
  4. For branch 535.x: upgrade to version 535.309.01 or later
  5. For branch 539.x: upgrade to version 539.72 or later
  6. For branch 580.x: upgrade to version 580.159.03 or later
  7. For branch 582.x: upgrade to version 582.53 or later
  8. Restart the system after driver installation to ensure the new driver loads properly
Caveat Driver updates may reset application/game settings to default; ensure backup of custom profiles before upgrade

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

Fix this in Gpu Display Driver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
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,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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