Loading vulnerability…
A denial of service vulnerability exists in Microsoft Hyper-V when the host server fails to properly validate specific malicious data originating from a user on a guest operating system. An attacker with a privileged account on a guest VM can exploit this by running a specially crafted application, causing Hyper-V to mishandle the data and potentially leading to a denial of service condition on the host.
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 a denial-of-service (DoS) vulnerability in Microsoft Hyper-V when nested virtualization is enabled. The exploit is implemented as a Windows kernel-mode driver project (Visual Studio 2019), with main code in 'hypervbsod.c', 'hypervenlightments.c', and supporting assembly in 'vmx.asm'. The driver, when executed inside a guest VM with nested virtualization enabled, manipulates virtualization hardware features (VMX operations) to trigger a crash (BSOD) or reboot on the Hyper-V host. The README provides setup instructions and mitigation advice (disabling nested virtualization on untrusted VMs). The exploit targets Hyper-V on Windows Server 2019, Windows 10 (latest patches), and Windows 10 Insider Preview build 10.0.20206.1000 and earlier. The main fingerprintable endpoints are the device object and symbolic link created by the driver ('\Device\hypervbsod', '\DosDevices\hypervbsod'). No network endpoints are present; the attack vector is local, requiring code execution within a guest VM.
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.