Loading vulnerability…
CVE-2019-5688 is a vulnerability in NVIDIA NVFlash, NVUFlash Tool (prior to v5.588.0), and GPUModeSwitch Tool (prior to 2019-11), specifically in the NVIDIA kernel mode drivers (nvflash.sys, nvflsh32.sys, and nvflsh64.sys). Authenticated users with administrative privileges can access device memory and registers of devices not managed by NVIDIA, potentially leading to privilege escalation, information disclosure, or denial of service.
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 single Python exploit script (exploit.py) targeting the NVFLASH device driver on Windows systems. The script leverages the DeviceIoControl interface to map and access physical memory through the NVFLASH driver (\\.\NVFLASH). It provides functions to read from and write to arbitrary physical memory addresses, effectively allowing kernel memory manipulation. The exploit demonstrates its capability by writing a test string to a physical address and reading it back. The code is a proof-of-concept and requires local access with sufficient privileges to interact with the device driver. No network endpoints are present; the attack vector is local, exploiting a vulnerable device driver interface.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.