dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2026-24194

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 in a kernel mode layer handler, where a user could cause improper permission handling. 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 vulnerability in a kernel mode layer handler where improper permission handling allows a user to potentially cause denial of service, privilege escalation, information disclosure, data tampering, or code execution.

MitigationApply the NVIDIA display driver security update once released by NVIDIA; ensure kernel mode driver components are patched according to vendor guidance.

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 to see the installed driver version
    Affected if The driver version falls within any of these ranges: 535.x < 535.309.01, 539.x < 539.72, 580.x < 580.159.03, 582.x < 582.53, 595.x < 595.36, or 595.x < 595.71.05
  2. Verify NVIDIA kernel module is loaded
    Run 'lsmod | grep nvidia' to confirm the nvidia kernel module is loaded
    Affected if The nvidia kernel module is loaded and the driver version is in the affected ranges from step 1
  3. Check for unprivileged user access to the system
    Determine if unprivileged users have shell access or can interact with the display driver (e.g., via X11/Wayland or CUDA)
    Affected if Unprivileged users can access the system AND the vulnerable driver version is installed
  4. Confirm the kernel mode layer is in use
    Check if the NVIDIA driver is actively handling graphics operations - look for nvidia_uvm, nvidia_modeset, or nvidia_drm modules via 'lsmod | grep nvidia'
    Affected if Kernel mode layer components are loaded and the driver version is in the affected ranges

You are affected if an unprivileged user can access the system AND an NVIDIA Linux display driver version within the affected ranges (535.x, 539.x, 580.x, 582.x, or 595.x below the patched versions) is installed with kernel mode layer components 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 display driver security update once released by NVIDIA; ensure kernel mode driver components are patched according to vendor guidance.

Recommended fix High confidence

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

  1. Identify the currently installed NVIDIA driver version using 'nvidia-smi' or checking /proc/driver/nvidia/version
  2. Determine which branch of driver you are running (535.x, 539.x, 580.x, or 582.x)
  3. For drivers in the 535 branch (versions 535.x): upgrade to version 535.309.01 or later
  4. For drivers in the 539 branch (versions 539.x): upgrade to version 539.72 or later
  5. For drivers in the 580 branch (versions 580.x): upgrade to version 580.159.03 or later, or alternatively to version 582.53 or later
  6. For drivers in the 582 branch (versions 582.x): upgrade to version 582.53 or later
  7. Download the appropriate driver from the official NVIDIA website (nvidia.com) or your Linux distribution's repository
  8. Install the new driver package using your distribution's package manager (e.g., apt, yum, dnf) or run the NVIDIA installer directly
Caveat Driver updates may require matching kernel version; verify kernel compatibility 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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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