CVE-2024-41041 is a race condition in the Linux kernel UDP socket lifecycle. In udp_lib_get_port(), a bound UDP socket was inserted into the UDP hash table before its SOCK_RCU_FREE flag was set. Concurrent UDP IPv4 or IPv6 early-demultiplexing and socket-lookup paths can retrieve the socket without acquiring a reference and rely on SOCK_RCU_FREE to establish that it is safe to access during an RCU grace period. The ordering permitted those paths to observe the socket before the safety flag was present, triggering a DEBUG_NET_WARN_ON_ONCE condition in udp_v4_early_demux(). The fix sets SOCK_RCU_FREE before inserting the socket into the hash table.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel UDP socket-lifecycle issue in udp_lib_get_port(), addressed by earlier setting of SOCK_RCU_FREE.
Linux kernel UDP lifecycle issue addressed by setting SOCK_RCU_FREE earlier in udp_lib_get_port().
UDP socket lifetime-management issue in Linux kernel port allocation.
Linux kernel UDP socket RCU-free state handling flaw.
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.