Loading vulnerability…
CVE-2024-47679 is a race condition in Linux kernel virtual filesystem inode handling involving evict_inodes(), find_inode(), and iput(). During filesystem shutdown, evict_inodes() checks an inode's reference count before acquiring its lock. Meanwhile, an inode released by iput() can remain on the superblock and hash lists with a zero reference count and without the I_FREEING or I_WILL_FREE flags. A concurrent lookup can acquire another reference before eviction obtains the lock. Because eviction does not recheck the reference count under the lock, two threads can subsequently evict the same inode, triggering kernel BUG assertions in clear_inode() or iput(). The issue was observed through Btrfs 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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel VFS race condition allows concurrent threads to evict the same inode because its reference count can change after an initial check. This can trigger kernel BUG conditions and cause denial of service. The reference assigns a CVSS v3 score of 4.7, with local access, low privileges, and high attack complexity. The fix rechecks inode->i_count while holding i_lock.
Linux kernel VFS inode-handling race condition.
Linux kernel VFS inode lifecycle race condition.
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.