Loading vulnerability…
CVE-2024-42271 is a use-after-free flaw in the Linux kernel af_iucv subsystem, specifically in iucv_sock_close(). The bug arises from a race around severing an IUCV path: iucv_sever_path() can be invoked from both process context and bottom-half/tasklet context, while iucv->path is used as the indicator for whether another execution context is already severing or has already removed the path. Because this state transition was not protected with an atomic compare-and-swap, there is a window in which iucv_sock_close() may continue operating on a path object that has already been severed and freed by iucv_callback_connrej() running via iucv_tasklet_fn(). The provided crash trace shows execution reaching iucv_path_sever() from iucv_sock_close(), culminating in a kernel panic. The upstream fix resolves the race by making the path handoff/removal atomic.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.