Skip to main content

NVIDIA GPU Driver EUVDEUVD-2026-90168

| CVE-2026-47492 MEDIUM
Missing Authorization (CWE-862)
2026-09-30 nvidia GHSA-x8m3-359c-5h7c
5.5
CVSS 3.1 · Vendor: nvidia
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local low-privileged account
  2. Exploit
    Invoke NVIDIA kernel-mode driver interface
  3. Execution
    Trigger improper access control (CWE-862)
  4. Impact
    Crash or hang GPU driver/host (DoS)

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires local access with a low-privileged account on a system running the affected NVIDIA GPU Display Driver (GeForce, RTX/Quadro/NVS, or Tesla) on Windows or Linux, or the affected Guest Driver/Virtual GPU Manager in a vGPU deployment; the attacker invokes the kernel-mode driver interface directly. Exploitation is LIMITED by the need for pre-existing local authenticated access (PR:L, AV:L - not remotely reachable) and by driver version: only versions prior to the fixed releases (e.g., GeForce < 580.178.04/616.56, RTX/Quadro/NVS < 610.88/615.71.09, vGPU <= 20.1) are affected, and for one GeForce branch only Maxwell, Volta, and Pascal architectures. Impact is capped at denial of service - no code execution, privilege escalation, or data disclosure is possible.

Impact

This is a genuinely low-to-moderate priority issue despite the 5.5 (Medium) CVSS. The vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H is internally consistent with the description: an already-authenticated local low-privileged user triggers a kernel-mode improper access control flaw (CWE-862) whose only impact is denial of service (A:H, with C:N and I:N confirming no data exposure or integrity loss). There is no EPSS score, no CISA KEV listing, and no public exploit identified at time of analysis, so there is no evidence of active exploitation or automated weaponization. The realistic worst case is a local user crashing/hanging the GPU driver or host - a stability/availability nuisance rather than a privilege-escalation or RCE threat. No signals conflict here: the CVSS local vector matches the 'kernel mode layer' local-trigger description and the DoS-only impact. The one caveat worth verifying with the vendor is the 'Authentication Bypass' tag, which overstates the outcome - CWE-862 is a missing-authorization (authz) weakness and the confirmed impact is DoS, not an authentication bypass.

Exploit ScenarioDerived

A local user with an unprivileged account on a Windows or Linux workstation or vGPU-backed VM issues a crafted request to the NVIDIA kernel-mode driver that the driver fails to properly authorize, causing the driver or host to crash or hang. No public proof-of-concept exists; exploitation yields only denial of service, not code execution or data access.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 30, 2026

Denial of service in the NVIDIA GPU Display Driver for Windows and Linux arises from improper access control (CWE-862) in the kernel-mode layer, where a local user with a low-privileged account can invoke a driver interface they should not be authorized to reach and thereby crash or hang the affected system. Impact is limited to availability: with the assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (base 5.5, Medium), exploitation requires pre-existing local authenticated access on a host running an affected driver branch - GeForce, RTX/Quadro/NVS, Tesla, or the vGPU Guest Driver/Virtual GPU Manager - and no remote path exists. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing), and no code execution, privilege escalation, or data disclosure is achievable, making this a low-to-moderate operational priority that is chiefly relevant to multi-user, VDI, and shared-workstation environments.

RemediationAI

Apply the vendor-released patch by upgrading to the fixed driver build for your branch as published by NVIDIA in its product-security advisory (https://github.com/NVIDIA/product-security/tree/main/2026/5861): GeForce users should move to 580.178.04 or later (or the applicable fixed release for their branch, such as 616.56), RTX/Quadro/NVS users to 610.88 or later (or 615.71.09 and later branch fixes), and Tesla users to 610.57.04 or later, noting that on the branch where only Maxwell, Volta, and Pascal architectures are impacted the fixed release is 582.78. For vGPU deployments, update both components - the Virtual GPU Manager (e.g., 596.38, superseding affected vGPU 19.5 and 20.1 builds) and the Guest Driver (e.g., 596.36) - and keep guest and host versions aligned, since mismatched pairs can leave the guest-side interface exposed. Until patching is completed, the practical compensating controls follow from the fact that the bug requires an already-authenticated low-privileged local session, so reducing the number of untrusted interactive logins is the highest-value measure: remove or disable unnecessary local accounts, avoid granting interactive or RDP access to shared GPU hosts (notably VDI and multi-tenant virtualization hosts, where the Guest Driver and Virtual GPU Manager expand the attack surface), and restrict who can open sessions on machines with sensitive workloads. The trade-off is reduced operational flexibility for shared-workstation and VDI use cases, and these measures do not eliminate the flaw - they only shrink the pool of potential local callers. Monitoring display-driver fault telemetry, system bugchecks/TDR resets, and unexpected GPU driver restarts can provide early warning of attempted abuse, though such signals are noisy and should be triaged against legitimate driver instability.

Affected VersionsENISA

GeForce All driver versions prior to 580.178.04
RTX, Quadro, NVS All driver versions prior to 610.88
GeForce All driver versions prior to 616.56
RTX, Quadro, NVS All driver versions prior to 615.71.09
Guest driver 580.159.03(All versions prior to and including vGPU 19.5)
RTX, Quadro, NVS All driver versions prior to 595.91.07
RTX, Quadro, NVS All driver versions prior to 580.178.04
RTX, Quadro, NVS All driver versions prior to 616.92
GeForce All driver versions prior to 582.78 Only GPUs based on the NVIDIA Maxwell, Volta, and Pascal GPU architectures are affected.
Tesla All driver versions prior to 615.71.09
RTX, Quadro, NVS All driver versions prior to 582.78
RTX, Quadro, NVS All driver versions prior to 610.57.04
Virtual GPU Manager 596.38(All versions prior to and including vGPU 20.1)
Tesla All driver versions prior to 616.92
Guest driver 595.71.05(All versions prior to and including vGPU 20.1)
GeForce All driver versions prior to 615.71.09
Tesla All driver versions prior to 596.86
GeForce All driver versions prior to 610.60
GeForce All driver versions prior to 610.57.04
Guest driver 582.53(All versions prior to and including vGPU 19.5)
Tesla All driver versions prior to 610.57.04
Tesla All driver versions prior to 580.178.04
RTX, Quadro, NVS All driver versions prior to 596.86
GeForce All driver versions prior to 595.91.07
Tesla All driver versions prior to 610.88
Guest driver 596.36(All versions prior to and including vGPU 20.1)
Virtual GPU Manager 582.51(All versions prior to and including vGPU 19.5)
Tesla All driver versions prior to 595.91.07
Virtual GPU Manager 580.159.01(All versions prior to and including vGPU 19.5)
Virtual GPU Manager 595.71.03(All versions prior to and including vGPU 20.1)

Affected Packages

euvd geforce_all_driver_versions_prior_to no fix
euvd rtx_quadro_nvs_all_driver_versions_prior_to no fix
euvd tesla_all_driver_versions_prior_to no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 3 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw sits in the kernel-mode layer of the NVIDIA display driver (the privileged component exposed as nvlddmkm.sys on Windows and the NVIDIA kernel modules on Linux) that services requests forwarded from user-mode graphics and compute APIs. CWE-862 (Missing Authorization) describes the root cause: an access-control check on a privileged driver entry point is absent or insufficient, so a caller holding only ordinary local user rights can reach an operation intended to be restricted. Because the vulnerable code runs in kernel mode, the observable consequence is a fault or resource exhaustion that terminates or destabilizes the operating system rather than a user-space crash. The affected CPE strings enumerate NVIDIA GeForce, NVIDIA RTX/Quadro/NVS, and NVIDIA Tesla product families, and the ENISA EUVD record additionally covers virtualization components - the vGPU Guest Driver and Virtual GPU Manager - where a guest-side caller interacts with the hypervisor-hosted GPU manager. As assessed, the primitives available to an attacker are bounded: the misconfiguration yields availability loss only (C:N/I:N/A:H), with no path demonstrated to memory corruption, code execution, or information leakage.

Know when Windows gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (nvidia) PRIMARY 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 5.5 MEDIUM

Local authenticated low-priv trigger of a kernel driver (AV:L/PR:L/AC:L), no interaction, no confidentiality or integrity impact, availability-only DoS (A:H).

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE HIGH
Red Hat 5.5 MEDIUM

Primary rating from Vendor (nvidia).

CVSS VectorVendor: nvidia

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

DescriptionCVE.org

NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where an attacker can cause improper access control. A successful exploit of this vulnerability might lead to denial of service.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
High
NVIDIA GeForce/RTX/Quadro/Tesla drivers ship on vast numbers of workstations and servers
Data Quality
5 sources
Confidence: Medium
EUVD NVD CVE.org EPSS Vulnrichment Vendor GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Micro 5.3 Affected
SUSE Linux Enterprise Micro 5.4 Affected
SUSE Linux Enterprise Micro 5.5 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy