CVE-2025-38566 affects server-side TLS alert processing in the Linux kernel SunRPC implementation used by NFS over TLS. The tls_alert_recv() function incorrectly assumes that alert data can be read from the message iterator's kvec. kTLS separates non-data TLS records between a control-message buffer containing the record type and a message payload buffer containing the remaining data, such as the alert level and description. Message copying can advance the iterator's kvec pointer, invalidating the assumptions made by the alert-processing code. The correction reworks control-message reception through sock_recvmsg() and reverts the iterator before invoking tls_alert_recv().
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.
10 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.