CVE-2025-40176
Published Nov 12, 2025
Modified Apr 15, 2026
Description
In the Linux kernel, the following vulnerability has been resolved: tls: wait for pending async decryptions if tls_strp_msg_hold fails Async decryption calls tls_strp_msg_hold to create a clone of the input skb to hold references to the memory it uses. If we fail to allocate that clone, proceeding with async decryption can lead to various issues (UAF on the skb, writing into userspace memory after the recv() call has returned). In this case, wait for all pending decryption requests.
Is your site exposed to CVE-2025-40176?
Run a free security scan — no signup, results in seconds.
References
Other References
https://git.kernel.org/stable/c/39dec4ea3daf77f684308576baf483b55ca7f160
https://git.kernel.org/stable/c/4fc109d0ab196bd943b7451276690fb6bb48c2e0
https://git.kernel.org/stable/c/9f83fd0c179e0f458e824e417f9d5ad53443f685
https://git.kernel.org/stable/c/b8a6ff84abbcbbc445463de58704686011edc8e1
https://git.kernel.org/stable/c/c61d4368197d65c4809d9271f3b85325a600586a
Frequently Asked Questions
What is CVE-2025-40176? +
In the Linux kernel, the following vulnerability has been resolved:
tls: wait for pending async decryptions if tls_strp_msg_hold fails
Async decryption calls tls_strp_msg_hold to create a clone of the
input skb to hold references to the memory it uses. If we fail to
allocate that clone, proceeding with async decryption can lead to
various issues (UAF on the skb, writing into userspace memory after
the recv() call has returned).
In this case, wait for all pending decryption requests.
How do I check if I'm vulnerable to CVE-2025-40176? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.