Loading vulnerability…
CVE-2024-41012 is a race condition in the Linux kernel file-locking subsystem. When fcntl_setlk() races with close(), the prior cleanup path attempted to remove a newly created POSIX lock through a second do_lock_file_wait() call. An LSM may permit the initial call that creates the lock while denying the subsequent call intended to remove it. In addition, POSIX-lock removal could fail when allocation required to split a lock range fails. A stale lock can consequently retain references to freed state, causing use-after-free reads in lock_get_status() when /proc/locks is read. The fix replaces this cleanup path with locks_remove_posix(), which reliably removes POSIX locks associated with the file and files_struct.
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.