Review reviewCritical

CVE-2025-40176

Linux

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.

CVSS
9.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2025.11.12
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 9.8

Vulnerability overview

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.

Affected product and versions

Product
Linux
Affected versions
>= 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 9f83fd0c179e0f458e824e417f9d5ad53443f685, >= 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < c61d4368197d65c4809d9271f3b85325a600586a, >= 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 39dec4ea3daf77f684308576baf483b55ca7f160, >= 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < 4fc109d0ab196bd943b7451276690fb6bb48c2e0, >= 84c61fe1a75b4255df1e1e7c054c9e6d048da417 < b8a6ff84abbcbbc445463de58704686011edc8e1, >= 6.0
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
Not available