Loading vulnerability…
CVE-2026-31467 is a Linux kernel denial-of-service vulnerability in the EROFS filesystem bio completion path. In process-context completion flows such as those involving dm-verity, bio completion can invoke decompression directly instead of deferring to a separate workqueue. That path may call vm_map_ram() with GFP_KERNEL. Under memory pressure, vm_map_ram() can trigger reclaim and swapping I/O; if this occurs while the bio completion path is already in a context that can reach submit_bio_wait(), the kernel can deadlock. The issue was resolved by wrapping the affected path with memalloc_noio_save() and memalloc_noio_restore() so memory allocation in that context does not initiate I/O recursion.
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.
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.