Loading vulnerability…
A vulnerability in the Realtek HAD kernel driver allows a local attacker to send a specially crafted string from user mode to the driver. The driver does not properly validate or sanitize the input, resulting in the execution of unexpected commands and a subsequent crash of the kernel driver, leading to a system crash (BSOD).
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 provides a proof-of-concept (POC) local exploit for CVE-2021-32537, a vulnerability in the Realtek RTKVHD64.sys audio driver for Windows. The exploit is implemented in C++ (src/cve-2021-32537.cc) and is designed to demonstrate two key capabilities: (1) leaking a kernel address of a KEVENT object via a custom IOCTL (0x225c0c), and (2) triggering a kernel crash (BSoD) by sending a specially crafted input buffer to IOCTL 0x225f04, which causes an out-of-bounds access and pool corruption in the driver. The exploit automatically locates the device path for the vulnerable driver using the Windows MMDevice API, opens a handle to the device, and performs the exploit steps. The README.md provides a detailed root cause analysis, affected hardware, and crash dump analysis. The repository is structured as a Visual Studio C++ project with a single main exploit source file, project files, and documentation. No remote/network attack vector is present; exploitation requires local code execution on a vulnerable Windows system.
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.