Loading vulnerability…
CVE-2025-21976 is a resource-release vulnerability in the Linux kernel's Hyper-V framebuffer driver, hyperv_fb. When a Hyper-V framebuffer device is unbound while its framebuffer remains in use, the driver's removal path attempts to release the framebuffer forcibly. This triggers a kernel warning in framebuffer_release and prevents the framebuffer from being released. The fix moves framebuffer and associated memory cleanup into the fb_ops.fb_destroy callback and replaces manual framebuffer registration and unregistration with devm_register_framebuffer.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel hyperv_fb driver vulnerability involving improper release of an in-use framebuffer during device removal. The flaw affects availability and has a CVSS v3 base score of 5.5, with local access and low privileges required. The fix moves framebuffer and associated memory cleanup to fb_ops.fb_destroy and uses devm_register_framebuffer for graceful lifecycle management.
Linux kernel Hyper-V framebuffer removal flaw.
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.