Loading vulnerability…
CVE-2026-23240 is a race condition in the Linux kernel TLS software transmit-work cancellation path, tls_sw_cancel_work_tx(). During TLS socket teardown, tls_sk_proto_close() previously used cancel_delayed_work_sync() to cancel transmit work. A concurrent write-space path, including processing associated with delayed ACKs or ksoftirqd, could schedule tx_work_handler() after cancellation completed. The TLS context could then be freed before the newly scheduled worker executes, causing tx_work_handler() to dereference freed kernel memory. The upstream correction replaces cancel_delayed_work_sync() with disable_delayed_work_sync(), preventing new scheduling of the delayed work during teardown.
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.
26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel TLS subsystem race condition in tls_sw_cancel_work_tx().
Linux kernel TLS subsystem race condition.
A race condition in the Linux kernel TLS software transmit-work cancellation path.
Linux kernel TLS subsystem race condition in tls_sw_cancel_work_tx().
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.