dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2026-24192

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 Linux contains a vulnerability where an attacker could cause an incorrect conversion between numeric types, leading to a heap buffer overflow. 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 Linux contains a type conversion vulnerability that leads to heap buffer overflow. An attacker could exploit this to corrupt heap memory, potentially achieving code execution, privilege escalation, or denial of service.

MitigationApply the latest NVIDIA display driver update from NVIDIA's official repository or website to obtain the patched version that addresses this vulnerability.

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 installed NVIDIA driver version
    Run 'nvidia-smi' or check /proc/driver/nvidia/version, or use 'ls -la /usr/lib/x86_64-linux-gnu/nvidia*/', or check package manager (dpkg -l | grep nvidia)
    Affected if The driver version falls within any of these ranges: 535.x versions below 535.309.01, 539.x versions below 539.72, 580.x versions below 580.159.03, 582.x versions below 582.53, 595.x versions below 595.36 or below 595.71.05
  2. Verify the driver is actively loaded
    Run 'lsmod | grep nvidia' to check if nvidia kernel modules are loaded, or check 'ls -la /dev/nvidia*' for device nodes
    Affected if The nvidia kernel modules are loaded and the driver version is vulnerable per the version check above
  3. Confirm the vulnerability trigger condition
    This is a local access vulnerability in the kernel-mode driver component. Any user with local access to a system running a vulnerable driver version could potentially trigger the type confusion during display driver operations
    Affected if Local untrusted users can access the system and the driver version is vulnerable

A system is affected if it runs any NVIDIA Linux display driver version within the ranges listed above, with the driver actively loaded.

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 latest NVIDIA display driver update from NVIDIA's official repository or website to obtain the patched version that addresses this vulnerability.

Recommended fix High confidence

Upgrade to NVIDIA Display Driver 535.309.01, 539.72, 580.159.03, or 582.53 (depending on your current major version branch)

  1. 1. Identify the current NVIDIA driver version by running 'nvidia-smi' or checking '/proc/driver/nvidia/version'
  2. 2. Determine which version branch your current driver belongs to (535.x, 536-539.x, or 580.x)
  3. 3. Download the appropriate fixed driver version from NVIDIA's official website (nvidia.com/drivers) or your distribution's package repository
  4. 4. Stop any graphical display manager (e.g., run 'sudo systemctl stop gdm' or 'sudo systemctl stop lightdm')
  5. 5. Uninstall the current driver: 'sudo apt-get remove nvidia-driver-*' (Debian/Ubuntu) or 'sudo yum remove nvidia-driver-*' (RHEL/CentOS)
  6. 6. Install the fixed driver package for your version: For 535 branch use 535.309.01, for 536-539 use 539.72, for 580 branch use 580.159.03 or 582.53
  7. 7. Reboot the system: 'sudo reboot'
  8. 8. Verify the new driver version loads correctly with 'nvidia-smi'
Caveat Driver upgrades may require kernel module recompilation; ensure kernel compatibility before upgrading; some legacy GPU models may not be supported in newer driver branches

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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