dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2026-24187

HIGH · 8.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 →
90/100
Remediation priority · Urgent
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 a use-after-free. 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 use-after-free vulnerability where the driver improperly handles memory pointers, continuing to access memory after it has been freed. This memory corruption can be exploited to potentially achieve code execution, privilege escalation, or denial of service.

MitigationApply the vendor-supplied patch or update to the NVIDIA display driver for Linux. Monitor NVIDIA's security bulletins for version-specific fixes and ensure testing in a staging environment before production deployment.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 'dpkg -l | grep nvidia' (Debian) or 'rpm -qa | grep nvidia' (RHEL)
    Affected if Installed version falls within 535.x before 535.309.01, 539.x before 539.72, 580.x before 580.159.03 or 582.53, or 595.x before 595.36 or 595.71.05
  2. Confirm NVIDIA kernel module is loaded
    Run 'lsmod | grep nvidia' to verify the nvidia kernel module is currently loaded
    Affected if The nvidia driver module is loaded and running (vulnerability only applies when driver is active)
  3. Check driver component version
    Run 'cat /sys/module/nvidia/version' or check 'modinfo nvidia' to get detailed driver build information
    Affected if Version output matches the affected version ranges above (535.x, 539.x, 580.x, or 595.x before respective fixes)
  4. Verify driver is being used
    Run 'nvidia-smi' to confirm the driver is functional and managing a GPU
    Affected if nvidia-smi executes successfully showing GPU information, confirming the driver is active and potentially vulnerable

You are affected if the NVIDIA Linux display driver version is 535.x before 535.309.01, 539.x before 539.72, 580.x before 580.159.03 or 582.53, or 595.x before 595.36 or 595.71.05 AND the driver is actively loaded/running.

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-supplied patch or update to the NVIDIA display driver for Linux. Monitor NVIDIA's security bulletins for version-specific fixes and ensure testing in a staging environment before production deployment.

Recommended fix High confidence

535.309.01 or later for 535.x branch; 580.159.03 or later for 580.x branch (or 539.72+/582.53+ respectively for alternate branches)

  1. 1. Identify the currently installed NVIDIA display driver version using 'nvidia-smi' or checking /proc/driver/nvidia/version
  2. 2. If running version 535.x (< 535.309.01 or < 539.72), upgrade to version 535.309.01 or later (or 539.72 or later for the 539.x branch)
  3. 3. If running version 580.x (< 580.159.03 or < 582.53), upgrade to version 580.159.03 or later (or 582.53 or later for the 582.x branch)
  4. 4. Download the appropriate driver from the official NVIDIA website or Linux distribution repository
  5. 5. Stop the display manager (e.g., 'systemctl stop gdm' for GNOME, 'systemctl stop lightdm' for LightDM)
  6. 6. Uninstall the current driver: 'sudo apt-get remove nvidia-driver-*' or 'sudo yum remove nvidia-driver-*'
  7. 7. Install the new driver package: 'sudo apt-get install nvidia-driver-535' (or appropriate version)
  8. 8. Reboot the system: 'sudo reboot'
Caveat Driver updates may require DKMS rebuild and could conflict with custom kernel modules; ensure backup of system and verify compatibility with specific GPU hardware before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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