CVE-2024-42246 is an infinite-loop denial-of-service vulnerability in the Linux kernel SunRPC TCP socket setup path. When a BPF program attached to kernel_connect() rejects a connection and returns -EPERM, xs_tcp_setup_socket() does not handle that error as a terminal network connection failure. The function can repeatedly retry socket setup, generating excessive syslog output and potentially causing the kernel to become unresponsive. The fix remaps -EPERM to -ECONNREFUSED for consistent handling by upper networking layers.
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.
Linux kernel net/sunrpc flaw involving EPERM handling after connection failures in xs_tcp_setup_socket.
A vulnerability addressed by the updated Red Hat Enterprise Linux 9 el9/flatpak-sdk container image; no technical details are provided in this advisory.
Linux kernel networking/SunRPC error-handling issue in xs_tcp_setup_socket during connection failures.
A Linux kernel networking/SUNRPC issue involving EPERM handling after connection failure in xs_tcp_setup_socket.
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.