LiveActive security incident?Get immediate response
CVE Record

CVE-2016-8817: All versions of NVIDIA Windows GPU Display Driver contain a vulnerability in the kernel mode layer (nvlddmk...

All versions of NVIDIA Windows GPU Display Driver contain a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgDdiEscape where a value passed from a user to the driver is used without validation as the size input to memcpy(), causing a buffer overflow, leading to denial of service or potential escalation of privileges.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a Windows NVIDIA GPU driver flaw where a local user-controlled value can trigger memory corruption in the kernel driver. The documented impact is system denial of service or possible privilege escalation. For executives, the main concern is endpoint hardening where users or workloads can run code on GPU-enabled Windows systems. Exposure is likely on Windows systems running affected NVIDIA GPU Display Drivers for Quadro, NVS, GeForce, GRID, or Tesla hardware. Practical priority is higher for shared workstations, VDI, lab machines, and systems where untrusted local users or workloads can execute code. Treat this as a high-priority legacy driver hygiene issue where GPU-enabled Windows systems are still in service. It is less urgent than a confirmed internet-exploited bug, but important for shared endpoints and environments with untrusted users. Mitigation focus: Review NVIDIA advisory 4257 for fixed driver versions and vendor instructions.; Update affected NVIDIA Windows GPU Display Drivers through official NVIDIA or OEM channels.; Prioritize shared Windows workstations, VDI hosts, and GPU-enabled multi-user systems..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-8817 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Nvidia CorporationQuadro, NVS, GeForce, GRID and TeslaAllListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.