Loading vulnerability…
CVE-2025-39682 is an improper-condition-check vulnerability in the Linux kernel TLS receive path. Each recvmsg() operation must process either contiguous DATA records or a single non-DATA record. An initial zero-length record retrieved from rx_list can bypass the intended record-type handling, causing subsequent records to be processed under incorrect zero-copy decryption and queuing assumptions. Zero-copy decryption writes plaintext directly into a user-space buffer, leaving no decrypted socket buffer available to queue when a record-type change requires deferred processing. The flaw affects systems using kernel TLS (kTLS) and may permit memory disclosure or denial of service.
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 (3 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.
79 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel TLS receive-path vulnerability involving zero-length records on rx_list and zero-copy decryption. The overlooked corner case disrupts record-type handling, potentially causing an attempt to queue a record after decryption directly into a user-space buffer. The plugin reports a critical CVSS v3 score of 9.8, although the vendor severity is LOW. Exploits are reported available, and a CISA Known Exploited Vulnerability remediation due date is listed.
A Linux kernel TLS receive-path vulnerability involving zero-length records queued on rx_list and zero-copy decryption. The advisory rates it critical, with a CVSS v3 base score of 9.8, reports available exploits, and lists a CISA Known Exploited Vulnerability remediation deadline of September 21, 2026.
A critical Linux kernel TLS receive-path vulnerability involving handling of zero-length records originating from the rx_list. Affected Google COS kernel packages require an update to remediate it.
A Linux kernel TLS receive-path logic flaw involving queued zero-length records, which can cause different TLS record types to be processed together when kTLS is used. Public exploits are reported to be available, and CISA confirmed active exploitation.
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.