CVE-2026-24190
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 · uneditedNVIDIA Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a user could cause improper access to GPU resources. 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 confidenceNVIDIA Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer where improper access to GPU resources can be exploited. This kernel-mode flaw enables a local user to potentially achieve denial of service, privilege escalation, information disclosure, data tampering, or arbitrary code execution.
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>= 535, < 535.309.01>= 535, < 539.72>= 580, < 580.159.03>= 580, < 582.53>= 595, < 595.36>= 595, < 595.71.05CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if NVIDIA GPU driver is installedOn Windows, open Device Manager and expand 'Display adapters' to see if an NVIDIA GPU is listed. On Linux, run 'lspci | grep -i nvidia' or 'nvidia-smi' to confirm NVIDIA driver presence.Affected if No NVIDIA GPU or driver is found, the system is not affected.
-
Determine the installed NVIDIA driver versionOn Windows, run 'nvidia-smi' from command prompt or check the driver properties in Device Manager. On Linux, run 'nvidia-smi' or 'cat /proc/driver/nvidia/version'. Note the full version number (e.g., 535.x, 580.x, 595.x).Affected if The driver version cannot be determined, further checks cannot be performed.
-
Verify the kernel driver is loaded and activeOn Windows, confirm nvlddmkm.sys is loaded by checking driver signing status or running 'driverquery /v | findstr nvlddmkm'. On Linux, run 'lsmod | grep nvidia' to verify nvidia.ko is loaded, or 'modinfo nvidia' to see driver details.Affected if The kernel driver (nvlddmkm.sys on Windows or nvidia.ko on Linux) is not loaded, the specific vulnerability path may not be exploitable.
-
Compare installed version against affected rangesMatch the installed version number to all listed ranges: >= 535 but < 535.309.01; >= 535 but < 539.72; >= 580 but < 580.159.03; >= 580 but < 582.53; >= 595 but < 595.36; >= 595 but < 595.71.05.Affected if The installed version falls within ANY of these version ranges, the system is potentially affected by this CVE.
If the NVIDIA driver version falls into any of the specified version ranges and the kernel driver is loaded, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped535.309.01539.72580.159.03
Apply NVIDIA's latest display driver updates for Windows and Linux once available. Prioritize updating systems with untrusted users or network-adjacent attack surfaces given the high severity and code execution potential.
NVIDIA GPU Display Driver 535.309.01, 539.72, 580.159.03, or 582.53 (depending on the branch in use)
- Identify the current NVIDIA GPU display driver version installed on the system
- For Windows: Open Device Manager > Display adapters > right-click GPU > Properties > Driver tab
- For Linux: Run 'nvidia-smi' or check /proc/driver/nvidia/version
- Download the appropriate fixed driver version from NVIDIA's official download page (nvidia.com/Download/index.aspx)
- Select the GPU product and operating system, then download version 535.309.01 (for 535.x branch), 539.72 (for 539.x branch), 580.159.03 or 582.53 (for 580.x branch)
- Backup important data before driver installation
- Uninstall the current display driver completely using DDU (Display Driver Uninstaller) in safe mode for Windows, or remove packages for Linux
- Install the new driver version and restart the system
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24190 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24190 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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