Loading vulnerability…
CVE-2025-21817 is a deadlock vulnerability in the Linux kernel block layer. Block-device sysfs store callbacks execute while the request queue is frozen. Several callbacks, including update_nr_requests, wbt, and scheduler, allocate memory using GFP_KERNEL, which can enter direct reclaim and potentially deadlock against the frozen queue. The fix establishes a NOIO allocation context around the sysfs store operations.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vulnerability included in Debian advisory DSA-6528-1. No vulnerability-specific technical details or severity are provided. The prescribed remediation is updating the affected kernel packages to the fixed Trixie source package version 6.12.111-1 and rebooting into the patched kernel.
A Linux kernel block-layer deadlock vulnerability caused by sysfs store callbacks allocating with GFP_KERNEL while a request queue is frozen, potentially triggering direct reclaim. The fix marks GFP_NOIO around sysfs ->store() operations.
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.