Loading vulnerability…
CVE-2024-43854 is an uninitialized-memory disclosure vulnerability in the Linux kernel block-integrity write path. Metadata prepared by bio_integrity_prep is allocated with kmalloc without zero initialization before being written to storage media. For protection-information metadata, disclosure is generally limited to the application-tag field unused by kernel-generated metadata; for non-PI metadata, the complete integrity buffer can contain and persist residual kernel memory. The fix uses zeroed allocations for integrity metadata associated with write 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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel block-layer integrity-buffer issue addressed by zero-initializing the buffer before it is written to media.
Linux kernel block-layer issue involving integrity-buffer initialization before writing data to media.
Linux kernel block-layer integrity-buffer initialization flaw that could write uninitialized data to media.
Linux kernel block-layer integrity-buffer initialization 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.