Loading vulnerability…
CVE-2024-47679 is a race condition in the Linux kernel Virtual Filesystem (VFS) inode lifecycle. An inode whose reference count reaches zero in iput() can remain visible on the superblock and inode hash lists before it is marked I_FREEING or I_WILL_FREE. Concurrent evict_inodes() processing can observe the zero count and defer while a concurrent find_inode() obtains another reference because the freeing flags are not yet set. The eviction path can subsequently mark the inode for freeing while the newly acquired reference is released, causing two execution contexts to evict the same inode. The fix rechecks i_count while holding the inode lock before eviction, closing the check-to-use race.
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.
1 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.