Loading vulnerability…
CVE-2025-40176 is a use-after-free vulnerability in the Linux kernel TLS subsystem's asynchronous decryption handling. Asynchronous decryption uses tls_strp_msg_hold to clone the input socket buffer (skb) and retain references to memory used by the outstanding operation. If cloning fails because of an allocation failure, the affected code can continue processing asynchronous decryptions without preserving the required lifetime of the input skb. This can result in use-after-free access to the skb or writes to userspace memory after the corresponding recv() operation has returned. The fix waits for all pending asynchronous decryption requests when tls_strp_msg_hold fails.
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 handling flaw addressed by waiting for pending asynchronous decryptions when tls_strp_msg_hold fails.
A Linux kernel TLS vulnerability related to pending asynchronous decryptions when tls_strp_msg_hold fails.
A Linux kernel TLS vulnerability related to handling pending asynchronous decryptions when tls_strp_msg_hold fails.
A Linux kernel TLS subsystem flaw involving pending asynchronous decryptions when tls_strp_msg_hold fails.
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.