Loading vulnerability…
CVE-2024-50294 is a race condition in the Linux kernel RxRPC client-call handling path. When a client call is aborted after it has been queued for connection but before the I/O thread processes it, rxrpc_disconnect_client_call() can remove the call from local->new_client_calls without holding client_call_lock. A concurrent race can cause other calls to disappear from the list, resulting in hanging calls. The fix acquires client_call_lock before removing a call from the list referenced by its wait_link.
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.
Missing locking in Linux kernel RxRPC that can cause hanging calls.
Linux kernel RxRPC locking flaw resulting in denial of service.
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.