Loading vulnerability…
A vulnerability exists in all versions of the NVIDIA Windows GPU Display Driver within the kernel mode layer handler for DxgDdiEscape. The vulnerability is due to improper validation of the size of an input buffer, which can be exploited to cause a denial of service or potentially escalate privileges.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (PoC) exploit for CVE-2016-8823, a vulnerability in NVIDIA graphics drivers on Windows. The main file, 'a.c', is a C program that attempts to trigger the vulnerability by sending a specially crafted buffer to the driver using the D3DKMTEscape function. The exploit is designed to cause a system crash (denial of service) and demonstrates the vulnerability rather than providing a weaponized or privilege escalation payload. The code is structured as a single main loop that repeatedly attempts to trigger the vulnerable code path in the driver. The only other file is a minimal README. No network or remote attack vectors are present; the exploit must be run locally on a system with the vulnerable driver.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.