Threats / Microsoft / CVE-2018-8406
CVE-2018-8406
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Microsoft DirectX Graphics Kernel (DXGKRNL) vulnerability
An elevation of privilege vulnerability in Microsoft's DirectX Graphics Kernel driver allows attackers to gain higher system privileges through improper memory object handling.
Verdict
Today item, not a backlog item.
This vulnerability enables local privilege escalation and has been actively exploited in ransomware campaigns. The memory handling flaw in DXGKRNL permits attackers to escalate from user-mode to kernel-level access, facilitating destructive payload deployment.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-28), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.03444 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, DirectX Graphics Kernel (DXGKRNL). Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-404 CWE-404 — weakness family: Resource / availability.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious application that triggers improper memory object handling in the DXGKRNL driver.
Business
An attacker gains kernel-level code execution on the victim's system.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I use kernel access to disable security controls and establish persistence mechanisms.
Business
Ransomware operators deploy encryption payloads with system-wide scope and resilience against removal.
3
Lateral reach — past segmentation narrative 3
Attacker
I encrypt critical business data and demand ransom payment.
Business
Operations halt, data becomes inaccessible, and financial extortion occurs.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05