CVE-2024-38663 is an improper initialization flaw in the Linux kernel blk-cgroup subsystem. Following the blkcg_rstat_flush() optimization that places each I/O-statistics instance on a blk-cgroup per-CPU linked list, blkcg_reset_stats() reset an entire statistics instance with memset(). This cleared the embedded linked-list state while the instance remained registered, corrupting the list. The fix resets only the counter portion of the I/O-statistics structure and preserves list linkage.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel block-control-group flaw that can cause list corruption while resetting I/O statistics.
Linux kernel block-cgroup list-corruption vulnerability associated with resetting I/O statistics.
Linux kernel block-cgroup list-corruption flaw related to resetting I/O statistics.
A Linux kernel block cgroup vulnerability that can cause list corruption when resetting I/O statistics.
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.