Loading vulnerability…
CVE-2024-41049 is a use-after-free race in the Linux kernel file-locking subsystem's posix_lock_inode path. The request pointer may be changed to reference a lock entry newly added to an inode lock list. Before trace_posix_lock_inode() executes, a concurrent task can free that lock entry, causing the tracepoint to access freed memory. The upstream correction invokes the tracepoint while holding the relevant spinlock, preventing concurrent release of the referenced lock entry.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
Potential use-after-free vulnerability in Linux kernel POSIX file locking, in posix_lock_inode.
A potential use-after-free vulnerability in the Linux kernel POSIX file-locking code, in posix_lock_inode.
A potential use-after-free vulnerability in the Linux kernel file-locking code, specifically posix_lock_inode.
A Linux kernel file-locking use-after-free race in posix_lock_inode tracing. The race could cause trace_posix_lock_inode() to access a lock that another task had freed. The fix moves the tracepoint inside the spinlock.
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.