In the Linux kernel, the following vulnerability has been resolved: tls: wait for pending async decryptions if tls_strp_msg_hold fails Async… (CVE-2025-40176)
A critical vulnerability in the Linux kernel's TLS async decryption implementation was resolved. The issue occurs when tls_strp_msg_hold fails to clone the input skb during async decryption, potentially leading to use-after-free (UAF) on the skb and unauthorized writes into userspace memory after the recv() call returns. The fix ensures that the kernel waits for all pending decryption requests if cloning fails, preventing these memory safety issues.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's TLS async decryption arises when the function tls_strp_msg_hold fails to create a clone of the input skb (socket buffer) to hold memory references. If this cloning fails and async decryption proceeds, it can cause use-after-free conditions on the skb and writes into userspace memory after the recv() call has returned. The resolved fix involves waiting for all pending decryption requests to complete if cloning fails, thereby preventing unsafe memory operations.
Potential Impact
Successful exploitation can lead to use-after-free conditions and unauthorized memory writes into userspace, which may result in system crashes, data corruption, or potential privilege escalation. The vulnerability affects confidentiality, integrity, and availability of the system, as indicated by the CVSS vector with high impact on all three.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users and administrators should apply the official kernel updates that include this fix. Since this is a kernel-level issue, upgrading to a patched kernel version is the recommended remediation. Patch status is not explicitly stated in the provided data; therefore, verify the vendor advisory or Linux kernel mailing lists for the exact fixed versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: tls: wait for pending async decryptions if tls_strp_msg_hold fails Async… (CVE-2025-40176)
Description
A critical vulnerability in the Linux kernel's TLS async decryption implementation was resolved. The issue occurs when tls_strp_msg_hold fails to clone the input skb during async decryption, potentially leading to use-after-free (UAF) on the skb and unauthorized writes into userspace memory after the recv() call returns. The fix ensures that the kernel waits for all pending decryption requests if cloning fails, preventing these memory safety issues.
CVSS v3.1
Score 9.8critical
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's TLS async decryption arises when the function tls_strp_msg_hold fails to create a clone of the input skb (socket buffer) to hold memory references. If this cloning fails and async decryption proceeds, it can cause use-after-free conditions on the skb and writes into userspace memory after the recv() call has returned. The resolved fix involves waiting for all pending decryption requests to complete if cloning fails, thereby preventing unsafe memory operations.
Potential Impact
Successful exploitation can lead to use-after-free conditions and unauthorized memory writes into userspace, which may result in system crashes, data corruption, or potential privilege escalation. The vulnerability affects confidentiality, integrity, and availability of the system, as indicated by the CVSS vector with high impact on all three.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users and administrators should apply the official kernel updates that include this fix. Since this is a kernel-level issue, upgrading to a patched kernel version is the recommended remediation. Patch status is not explicitly stated in the provided data; therefore, verify the vendor advisory or Linux kernel mailing lists for the exact fixed versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-79rw-jwgh-qv55
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-40176"]
- Database Specific Severity
- CRITICAL
- Cvss Version
- 3.1
Threat ID: 6a6b72d69c2644c7f847a573
Added to database: 07/30/2026, 15:50:46 UTC
Last enriched: 07/30/2026, 16:54:22 UTC
Last updated: 09/13/2026, 22:01:29 UTC
Views: 36
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.