CVE-2024-26740 is a deadlock vulnerability in the Linux kernel traffic-control mirroring and redirect action implementation in net/sched. An egress-to-ingress redirect can cause a packet to re-enter the receive path inline and reach the socket that originated it while that socket's lock remains held. This can result in a tcp_v4_rcv-to-tcp_v4_rcv locking deadlock. The upstream fix queues packets through the receive backlog for all egress-to-ingress mirred reversals instead of processing the ingress receive path inline.
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.
A flaw in the Linux kernel net/sched act_mirred ingress processing path.
A CVE referenced by the OpenShift Container Platform 4.17.19 advisory; the content provides no vulnerability-specific description.
A Linux kernel networking traffic-control (net/sched) act_mirred issue affecting mirrored ingress traffic; the resolution changes act_mirred to use the backlog for mirred ingress.
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.