Loading vulnerability…
CVE-2025-39682 is a use-after-free vulnerability in the Linux kernel kTLS software receive path. The flaw occurs in TLS recvmsg() processing when an initial zero-length decrypted TLS record is obtained from the receive list during zero-copy handling. A subsequent record-type transition can cause the stream parser anchor SKB to be incorrectly re-queued to the TLS receive list even though zero-copy decryption has placed plaintext directly in user space and the anchor is not valid for re-queuing. This corrupts SKB list and reference-count state; later receive-resource cleanup on socket close can traverse freed memory. The issue affects kernel versions reported as 6.0 through 6.16.3, including 6.17 release candidates 1 and 2.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a full exploit chain for CVE-2025-39682, a Linux kernel vulnerability related to TLS zero-length record handling. The exploit targets the kernelCTF mitigation-v4-6.6 instance and is a variant of a previous CVE-2024-58239 exploit. The main exploit logic is implemented in C/C++ files under 'exploit/mitigation-v4-6.6/', with 'client.cpp' orchestrating the attack and 'server.cpp' acting as a malicious TLS server. The exploit works by abusing kernel heap management and overwriting '/proc/sys/kernel/core_pattern' to execute a root shell upon a controlled crash, thus achieving privilege escalation. Python scripts ('calc_AC_rate.py', 'test.py') automate the exploitation process and measure success rates. The exploit requires network connectivity between the attacker and the target, and uses UNIX domain sockets for heap spraying. The repository also includes scripts for compiling, running in QEMU, and debugging. The exploit is operational, with a reported success rate of 79%. The main fingerprintable endpoints are the core_pattern file, UNIX socket paths in /tmp, and the server's network binding to 0.0.0.0. The payload is a root shell executed via core_pattern hijacking.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel TLS flaw involving handling of zero-length records on the receive list (rx_list).
Linux kernel TLS flaw in handling zero-length records on the receive list.
A Linux kernel TLS flaw in handling zero-length records on the receive list (rx_list). It is addressed in the Red Hat kernel-rt update.
A Linux kernel TLS flaw in handling zero-length records on the receive list.
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.