cbcvebase.
CVE-2026-31533
published 2026-04-23

CVE-2026-31533: In the Linux kernel, the following vulnerability has been resolved: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption The -EBUSY handling…

PriorityP342critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.39%
31.6th percentile
In the Linux kernel, the following vulnerability has been resolved: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption The -EBUSY handling in tls_do_encryption(), introduced by commit 859054147318 ("net: tls: handle backlogging of crypto requests"), has a use-after-free due to double cleanup of encrypt_pending and the scatterlist entry. When crypto_aead_encrypt() returns -EBUSY, the request is enqueued to the cryptd backlog and the async callback tls_encrypt_done() will be invoked upon completion. That callback unconditionally restores the scatterlist entry (sge->offset, sge->length) and decrements ctx->encrypt_pending. However, if tls_encrypt_async_wait() returns an error, the synchronous error path in tls_do_encryption() performs the same cleanup again, double-decrementing encrypt_pending and double-restoring the scatterlist. The double-decrement corrupts the encrypt_pending sentinel (initialized to 1), making tls_encrypt_async_wait() permanently skip the wait for pending async callbacks. A subsequent sendmsg can then free the tls_rec via bpf_exec_tx_verdict() while a cryptd callback is still pending, resulting in a use-after-free when the callback fires on the freed record. Fix this by skipping the synchronous cleanup when the -EBUSY async wait returns an error, since the callback has already handled encrypt_pending and sge restoration.

Affected

84 ranges· showing 25
VendorProductVersion rangeFixed in
linuxlinux
linuxlinux
linuxlinux>= 13eca403876bbea3716e82cdfe6f1e6febb38754 < 0e43e0a3c94044acc74b8e0927c27972eb5a59e80e43e0a3c94044acc74b8e0927c27972eb5a59e8
linuxlinux>= 3ade391adc584f17b5570fd205de3ad029090368 < 414fc5e5a5aff776c150f1b86770e0a25a35df3a414fc5e5a5aff776c150f1b86770e0a25a35df3a
linuxlinux>= 5.15.160 < 5.15.2035.15.203
linuxlinux>= 6.1.84 < 6.1.1696.1.169
linuxlinux>= 6.6.18 < 6.6.1356.6.135
linuxlinux>= 6.7.6 < 6.86.8
linuxlinux>= 8590541473188741055d27b955db0777569438e3 < aa9facde6c5005205874c37db3fd25799d741bafaa9facde6c5005205874c37db3fd25799d741baf
linuxlinux>= 8590541473188741055d27b955db0777569438e3 < 5d70eb25b41e9b010828cd12818b06a0c3b044125d70eb25b41e9b010828cd12818b06a0c3b04412
linuxlinux>= 8590541473188741055d27b955db0777569438e3 < 2694d408b0e595024e0fc1d64ff9db0358580f742694d408b0e595024e0fc1d64ff9db0358580f74
linuxlinux>= 8590541473188741055d27b955db0777569438e3 < a9b8b18364fffce4c451e6f6fd218fa4ab646705a9b8b18364fffce4c451e6f6fd218fa4ab646705
linuxlinux>= cd1bbca03f3c1d845ce274c0d0a66de8e5929f72 < 02f3ecadb23558bbe068e6504118f1b712d4ece002f3ecadb23558bbe068e6504118f1b712d4ece0
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 5.15.160 < 5.15.2035.15.203
linuxlinux_kernel>= 6.1.84 < 6.1.1696.1.169
linuxlinux_kernel>= 6.13 < 6.18.236.18.23
linuxlinux_kernel>= 6.19 < 6.19.136.19.13

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_ubuntu7.8HIGH
vendor_redhat7.0MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.