Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Obtain local low-priv account on GPU host
  2. Delivery
    Craft malicious driver ioctl/command
  3. Exploit
    Trigger untrusted pointer dereference in kernel driver
  4. Execution
    Driver reads OOB memory or faults
  5. Impact
    Kernel info disclosure or system DoS

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
MITRE ATT&CK

2 techniques across 2 tactics: Execution, 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 the attacker to already have local access with a low-privilege authenticated account (PR:L) on a system running the NVIDIA GPU Display Driver kernel-mode component on Windows or Linux; no user interaction is needed. Exploitation is limited to local vectors only (AV:L) - there is no remote or network path - so the attacker must first obtain code execution or an interactive session on the GPU host. Impact is bounded to denial of service and information disclosure (no integrity/write primitive), so this cannot by itself yield privilege escalation or code execution. Multi-user, VDI, and cloud-GPU deployments where untrusted users share a GPU host are the most exposed configurations.

Impact

The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H, 7.1) describes a local, low-complexity attack requiring only low-privilege (authenticated) access with no user interaction, yielding high confidentiality and availability impact but no integrity impact - consistent with an untrusted-pointer dereference that can crash the driver (DoS) or leak kernel memory (info disclosure) without granting write/code-execution primitives. There is no EPSS score, no CISA KEV listing, and no public POC in the provided data, so exploitation status is 'no public exploit identified at time of analysis.' This is NVIDIA-reported (bulletin 5861) with a patch available, indicating an internally/coordinated-discovered defect rather than opportunistic exploitation. Realistically this is a MEDIUM-priority local privilege-adjacent bug: the local-only vector (AV:L) sharply limits mass exploitability, and the absence of integrity impact plus no code-execution claim (unlike sibling UAF/type-confusion CVEs in the same bulletin) makes it lower-value than the 7.8 RCE-adjacent NVIDIA siblings. No signals conflict; the vector and description are mutually consistent (DoS↔A:H, info disclosure↔C:H, no writeable primitive↔I:N).

Exploit ScenarioDerived

A local low-privileged user on a Windows or Linux workstation or a multi-tenant/VDI/cloud-GPU host issues crafted calls to the NVIDIA kernel-mode GPU driver that cause it to dereference an attacker-influenced untrusted pointer. This either crashes the driver/system (denial of service) or reads out-of-bounds kernel memory that is disclosed back to the attacker. No public exploit code is identified, and the local attack vector requires the attacker to already have code execution on the host.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% 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 and kernel memory disclosure in the NVIDIA GPU Display Driver for Windows and Linux let a local, low-privileged user who already holds an interactive session on the host force the kernel-mode component to dereference an untrusted pointer, crashing the driver or leaking kernel memory. The flaw is scored CVSS 3.1 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H) - a local-only, low-complexity attack requiring low-privilege authenticated access with no user interaction, delivering high confidentiality and availability impact but no integrity or write primitive, so it cannot by itself be chained into privilege escalation or code execution. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing); the most exposed deployments are multi-user, VDI, and cloud-GPU hosts where untrusted users share a GPU, since the attacker must first obtain code execution or an interactive session on the GPU host.

RemediationAI

Patch available per vendor advisory: NVIDIA's product-security bulletin for this issue (https://github.com/NVIDIA/product-security/tree/main/2026/5861, referenced alongside https://nvd.nist.gov/vuln/detail/CVE-2026-47602) should be used to identify the fixed driver build for your branch, and the updated GeForce, RTX/Quadro/NVS, or Tesla driver - plus the Virtual GPU Manager package where applicable - should be installed and the host rebooted, since kernel-mode driver updates cannot take effect without reloading. Because the provided data does not include the exact fixed version string, do not assume any specific version number; verify against the bulletin's version table before declaring remediation complete. Where immediate driver upgrade is not possible, compensating controls should target the precondition that the attacker must already have a local low-privilege session: restrict interactive logon and RDP/console access to GPU hosts to trusted identities, and isolate or de-privilege shared GPU use (dedicated vGPU profiles per tenant, no shared interactive sessions on VDI/cloud-GPU instances), accepting the operational cost of tighter GPU allocation. On Linux, loading only the driver components you actually need and confining untrusted workloads (containers, unprivileged users) away from direct /dev/nvidia* device access reduces the attack surface but does not eliminate the flaw, and it will break GPU acceleration for those workloads. In multi-tenant environments, monitor GPU host logs for driver resets (TDR events on Windows, Xid errors on Linux) as possible indicators of exploitation attempts, and note there is no confirmed active exploitation and no public exploit code identified at time of analysis, so prioritization should follow standard risk-based patching rather than emergency response.

Affected VersionsENISA

Tesla All driver versions prior to 596.86
GeForce All driver versions prior to 580.178.04
GeForce All driver versions prior to 610.57.04
Tesla All driver versions prior to 615.71.09
Virtual GPU Manager 582.51(All versions prior to and including vGPU 19.5)
RTX, Quadro, NVS All driver versions prior to 596.86
RTX, Quadro, NVS All driver versions prior to 615.71.09
GeForce All driver versions prior to 615.71.09
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 580.178.04
Tesla All driver versions prior to 616.92
RTX, Quadro, NVS All driver versions prior to 610.88
RTX, Quadro, NVS All driver versions prior to 580.178.04
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)
RTX, Quadro, NVS All driver versions prior to 616.92
GeForce All driver versions prior to 610.60
Virtual GPU Manager 595.71.03(All versions prior to and including vGPU 20.1)
Virtual GPU Manager 580.159.01(All versions prior to and including vGPU 19.5)
Tesla All driver versions prior to 595.91.07
RTX, Quadro, NVS All driver versions prior to 582.78
GeForce All driver versions prior to 616.56
Tesla All driver versions prior to 610.88
GeForce All driver versions prior to 595.91.07
Tesla All driver versions prior to 610.57.04
RTX, Quadro, NVS All driver versions prior to 595.91.07

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 vulnerable component is the NVIDIA GPU Display Driver's kernel-mode driver (kernel mode driver, or KMD) as it runs on Windows and Linux, with CPE entries covering the GeForce, RTX/Quadro/NVS, and Tesla driver families plus the virtual GPU Manager tag. The root cause is tracked as CWE-119, improper restriction of operations within the bounds of a memory buffer, and in practice manifests as the driver dereferencing a pointer value supplied or influenced by a local caller without validating it first - a classic untrusted-pointer dereference inside kernel space. Because the code executes at ring 0, a malformed or attacker-controlled pointer can either fault the driver (availability impact, observed as a TDR/driver reset or Xid error on the GPU) or return contents of kernel memory to the caller (confidentiality impact). The provided CVSS vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H confirms the attacker needs only local, low-privilege access and no victim interaction, and that the scope stays unchanged with no integrity component, which is consistent with a read/crash primitive rather than a controllable memory-write primitive. Multi-tenant GPU hosts - VDI sessions, shared workstations, and cloud GPU instances - are the configurations where a low-privileged local user is most likely to be present alongside other tenants' data.

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 7.1 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
vuln.today AI 7.1 HIGH

Local low-priv user (AV:L/PR:L) triggers an untrusted pointer dereference reliably (AC:L) causing kernel info disclosure (C:H) and driver crash (A:H) with no write primitive (I:N).

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

Primary rating from Vendor (nvidia).

CVSS VectorVendor: nvidia

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

DescriptionCVE.org

NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode driver where a local user can cause the driver to dereference an untrusted pointer. A successful exploit of this vulnerability might lead to denial of service and information disclosure.

Executive ViewAI

Why It Matters

NVIDIA GPU Display Driver for Windows and Linux is affected by a high-severity local denial-of-service and kernel memory disclosure vulnerability (CVE-2026-47602). An authenticated low-privileged user with an interactive session can crash the driver or leak kernel memory, disrupting GPU-accelerated workloads and potentially exposing sensitive data. Organizations running multi-user, VDI, or cloud-GPU hosts are most at risk, and with no vendor-released patch identified at time of analysis, security teams should urgently limit local access to these systems.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting interactive access to GPU hosts to trusted users, isolating multi-tenant GPU environments, monitoring for driver crashes and kernel memory disclosure, and applying any NVIDIA workarounds when available.

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
High
NVIDIA GeForce/RTX/Quadro/NVS/Tesla drivers on widely deployed Windows and Linux GPU hosts
Data Quality
4 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 HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

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

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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