tls: wait for pending async decryptions if tls_strp_msg_hold fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux 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.
From the CVE record · Linux
The Linux kernel’s TLS async decryption path can fail to clone an input buffer while retaining references to its memory. If decryption proceeds after that failure, it can cause a use-after-free or write to userspace memory after recv() returns. The input does not specify attacker access or authentication requirements.
Engineers running Linux kernels with TLS async decryption should check their versions against the vendor advisory; affected versions are not specified.