Loading vulnerability…
CVE-2025-71072 is a Linux kernel flaw in the shmem/tmpfs rename handling path. The issue affects recovery logic in rename and rename_exchange operations when maple_tree insertions fail under severe memory pressure. In particular, simple_offset_rename() and simple_offset_rename_exchange() do not correctly recover from insertion failures, and shmem_rename2() can reach an invalid state because shmem_whiteout() assumes the operation will successfully proceed to d_move() once whiteout creation has succeeded. The fix avoids potentially failing operations after whiteout creation by preinserting the target entry into the destination directory tree and reordering operations so that subsequent mtree_store() calls operate on already-present singleton entries that cannot fail in the same way. The vulnerability can lead to inconsistent directory-entry state and failed rename processing in shmem-backed filesystems.
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.