dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2026-24195

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to 535.309.01 / 539.72 or later.
See remediation →
57/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 in UVM, where a user could cause improper input validation. A successful exploit of this vulnerability might lead to denial of service.

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 an improper input validation vulnerability in the UVM (Unified Virtual Memory) component. A local user could exploit this to cause improper input handling, potentially leading to denial of service.

MitigationApply the NVIDIA driver update or patch corresponding to this CVE. For production systems, test the patched driver thoroughly to ensure compatibility with existing workloads and validate that the input validation fix does not introduce regressions.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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. Check if NVIDIA driver is installed
    Run `lsmod | grep -E 'nvidia|uvm'` to list loaded NVIDIA kernel modules, or run `nvidia-smi` to query the driver
    Affected if No NVIDIA modules are loaded or nvidia-smi fails, the driver is not installed
  2. Obtain the installed driver version
    Run `nvidia-smi` and look for the 'Driver Version' field in the output
    Affected if The driver version shown cannot be determined or is not displayed
  3. Compare driver version against affected ranges
    Match your driver version against: 535.x (< 535.309.01), 539.x (< 539.72), 580.x (< 580.159.03), 582.x (< 582.53), 595.x (< 595.36), 595.71.x (< 595.71.05)
    Affected if The installed version falls within any of these vulnerable ranges: 535.x before 535.309.01, 539.x before 539.72, 580.x before 580.159.03, 582.x before 582.53, 595.x before 595.36, or 595.71.x before 595.71.05
  4. Check if UVM component is in use
    Run `lsmod | grep nvidia_uvm` to see if the UVM kernel module is loaded; alternatively, check /proc/driver/nvidia-uvm if it exists
    Affected if The UVM module is loaded (visible in lsmod output) - this is the component with the vulnerability

You are affected if you have an NVIDIA GPU with a Linux display driver version in the vulnerable ranges AND the UVM module is loaded or available on your system.

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 driver update or patch corresponding to this CVE. For production systems, test the patched driver thoroughly to ensure compatibility with existing workloads and validate that the input validation fix does not introduce regressions.

Recommended fix High confidence

Upgrade to 535.309.01 (for 535.x branch), 539.72 (for 539.x branch), 580.159.03 (for 580.x branch), or 582.53 (for 582.x branch) - choose the version appropriate for your environment

  1. Identify the currently installed NVIDIA driver version using `nvidia-smi` or checking `/proc/driver/nvidia/version`
  2. Determine which version branch you are on (535, 539, 580, or 582 series)
  3. Download the appropriate fixed driver version from NVIDIA's official download page (nvidia.com)
  4. Ensure the system is in a stable state and close any graphics-intensive applications
  5. Install the new driver using the NVIDIA installer: `sudo ./NVIDIA-Linux-x86_64-<version>.run` or via package manager if using a repository
  6. Reboot the system to load the new driver
  7. Verify the new driver version is installed correctly using `nvidia-smi`
Caveat Driver upgrades require system reboot; ensure compatibility with your Linux kernel version 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 / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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