Loading vulnerability…
CVE-2026-46160 is a Linux kernel Btrfs flaw in directory removal handling. When a directory is removed, Btrfs fails to update the directory inode's last_unlink_trans field. This can cause incorrect fsync behavior if a process still holds an open file descriptor to the removed directory and calls fsync() on it after rmdir(). In the documented sequence, after prior directory modifications and fsync activity, a directory is emptied, opened, removed with rmdir(2), then fsync'd via the still-open descriptor; if a crash or power failure occurs afterward, Btrfs tree-log replay on the next mount can reconstruct inconsistent metadata. The reported failure manifests during mount-time log replay with -EIO and corruption diagnostics such as an invalid directory link count in a leaf, indicating filesystem metadata inconsistency introduced by the stale unlink transaction state.
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.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.