dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2026-24196

HIGH · 7.1 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to 535.309.01 / 539.72 or later.
See remediation →
73/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 Linux contains a vulnerability where a user could cause an out-of-bounds read. A successful exploit of this vulnerability might lead to denial of service and information disclosure.

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 · low confidence

NVIDIA Display Driver for Linux contains an out-of-bounds read vulnerability that could allow a local or potentially remote attacker to read memory beyond allocated buffers. This could lead to denial of service through driver instability or information disclosure of sensitive memory contents.

MitigationApply the NVIDIA vendor patch when released. Until then, restrict access to graphics driver interfaces and monitor for indicators of exploitation. Consider disabling the display driver if not required in production environments.

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
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Verify NVIDIA driver is installed on Linux
    Run 'lsmod | grep nvidia' to confirm the NVIDIA kernel module is loaded, or check for nvidia-smi at /usr/bin/nvidia-smi
    Affected if The NVIDIA kernel module is not loaded or nvidia-smi is not present - the vulnerability only applies if the NVIDIA display driver is installed and active
  2. Retrieve the installed driver version
    Execute 'nvidia-smi' and note the Driver Version field, or run 'cat /proc/driver/nvidia/version'
    Affected if Cannot retrieve a version number - the driver may not be properly installed
  3. Compare against affected version ranges
    Check if the installed version falls within any of these ranges: 535.x (less than 535.309.01), 539.x (less than 539.72), 580.x (less than 580.159.03), 580.x (less than 582.53), 595.x (less than 595.36), or 595.x (less than 595.71.05)
    Affected if The installed version is within any of the affected ranges listed above - the system is potentially vulnerable
  4. Confirm the display driver component is in use
    Check if the nvidia-drm or nvidia-modeset kernel modules are loaded with 'lsmod | grep -E "nvidia-drm|nvidia-modeset"'
    Affected if These display-related modules are loaded - the vulnerable display driver component is active and the flaw could be triggered

You are affected if the NVIDIA display driver for Linux is installed with a version matching any of the specified affected ranges and the nvidia-drm or nvidia-modeset display modules are 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 NVIDIA vendor patch when released. Until then, restrict access to graphics driver interfaces and monitor for indicators of exploitation. Consider disabling the display driver if not required in production environments.

Recommended fix High confidence

535.309.01 (for 535 branch), 539.72 (for 539 branch), or 580.159.03/582.53 (for 580 branch)

  1. 1. Identify the currently installed NVIDIA display driver version by running 'nvidia-smi' or checking /proc/driver/nvidia/version
  2. 2. Determine which branch (535, 539, or 580) your current version belongs to
  3. 3. For 535.x branch: upgrade to version 535.309.01 or later
  4. 4. For 539.x branch: upgrade to version 539.72 or later
  5. 5. For 580.x branch: upgrade to version 580.159.03 or later (or 582.53 or later for the alternative fix)
  6. 6. Download the appropriate driver from NVIDIA's official website or Linux distribution repository
  7. 7. Stop the display manager (e.g., 'sudo systemctl stop gdm' or 'sudo service lightdm stop')
  8. 8. Kill any running NVIDIA processes: 'sudo killall nvidia-smi' if applicable
Caveat Driver upgrades may require X server restart; ensure backup of display configuration; some legacy GPU models may not be supported in newer branches

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
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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