CVE-2024-44935 is a race condition in the Linux kernel SCTP implementation's reuseport handling. SCTP did not synchronize reuseport group allocation, socket addition, and socket detachment for sockets in the same SO_REUSEPORT group. During a concurrent listener creation and close sequence, reuseport_add_sock() can access a peer socket's sk_reuseport_cb after reuseport_detach_sock() has cleared it, causing a null-pointer dereference. Concurrent listen operations can also create duplicate reuseport groups; only one group receives traffic while the others become inactive. The fix applies hash-bucket locking to SCTP endpoint hash and unhash operations, consistent with TCP and UDP synchronization.
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.
A null-pointer dereference in the Linux kernel SCTP reuseport_add_sock() path.
Linux kernel SCTP NULL-pointer dereference in reuseport socket handling.
Linux kernel SCTP NULL-pointer dereference in reuseport socket handling.
Linux kernel SCTP NULL-pointer dereference in reuseport_add_sock.
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.