CVE-2026-31533 | Linux Kernel up to 6.19.12 tls tls_do_encryption use after free

VDB-359162 · CVE-2026-31533 · GCVE-0-2026-31533 LINUX KERNEL UP TO 6.19.12 TLS TLS_DO_ENCRYPTION USE AFTER FREE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.6 $5k-$25k 4.16+ Summaryinfo A vulnerability was found in Linux Kernel up to 6.19.12. It has been declared as critical. Affected by this issue is the function tls_do_encryption of the component tls. Such manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2026-31533. No exploit exists. It is recommended to upgrade the affected component. Detailsinfo A vulnerability was found in Linux Kernel up to 6.19.12. It has been rated as critical. Affected by this issue is the function tls_do_encryption of the component tls. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. CVE summarizes: 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. The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-31533 since 03/09/2026. The exploitation is known to be easy. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 04/23/2026). Upgrading to version 5.15.203, 6.1.169, 6.6.135, 6.12.82, 6.18.23 or 6.19.13 eliminates this vulnerability. Applying the patch 414fc5e5a5aff776c150f1b86770e0a25a35df3a/0e43e0a3c94044acc74b8e0927c27972eb5a59e8/aa9facde6c5005205874c37db3fd25799d741baf/5d70eb25b41e9b010828cd12818b06a0c3b04412/2694d408b0e595024e0fc1d64ff9db0358580f74/a9b8b18364fffce4c451e6f6fd218fa4ab646705 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Type Operating System Vendor Linux Name Kernel Version 5.15.202 6.1.168 6.6.134 6.12.0 6.12.1 6.12.2 6.12.3 6.12.4 6.12.5 6.12.6 6.12.7 6.12.8 6.12.9 6.12.10 6.12.11 6.12.12 6.12.13 6.12.14 6.12.15 6.12.16 6.12.17 6.12.18 6.12.19 6.12.20 6.12.21 6.12.22 6.12.23 6.12.24 6.12.25 6.12.26 6.12.27 6.12.28 6.12.29 6.12.30 6.12.31 6.12.32 6.12.33 6.12.34 6.12.35 6.12.36 6.12.37 6.12.38 6.12.39 6.12.40 6.12.41 6.12.42 6.12.43 6.12.44 6.12.45 6.12.46 6.12.47 6.12.48 6.12.49 6.12.50 6.12.51 6.12.52 6.12.53 6.12.54 6.12.55 6.12.56 6.12.57 6.12.58 6.12.59 6.12.60 6.12.61 6.12.62 6.12.63 6.12.64 6.12.65 6.12.66 6.12.67 6.12.68 6.12.69 6.12.70 6.12.71 6.12.72 6.12.73 6.12.74 6.12.75 6.12.76 6.12.77 6.12.78 6.12.79 6.12.80 6.12.81 6.18.0 6.18.1 6.18.2 6.18.3 6.18.4 6.18.5 6.18.6 6.18.7 6.18.8 6.18.9 6.18.10 6.18.11 6.18.12 6.18.13 6.18.14 6.18.15 6.18.16 6.18.17 6.18.18 6.18.19 6.18.20 6.18.21 6.18.22 6.19.0 6.19.1 6.19.2 6.19.3 6.19.4 6.19.5 6.19.6 6.19.7 6.19.8 6.19.9 6.19.10 6.19.11 6.19.12 License open-source Website Vendor: https://www.kernel.org/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 8.0 VulDB Meta Temp Score: 7.6 VulDB Base Score: 8.0 VulDB Temp Score: 7.6 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Use after free CWE: CWE-416 / CWE-119 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Partially Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Kernel 5.15.203/6.1.169/6.6.135/6.12.82/6.18.23/6.19.13 Patch: 414fc5e5a5aff776c150f1b86770e0a25a35df3a/0e43e0a3c94044acc74b8e0927c27972eb5a59e8/aa9facde6c5005205874c37db3fd25799d741baf/5d70eb25b41e9b010828cd12818b06a0c3b04412/2694d408b0e595024e0fc1d64ff9db0358580f74/a9b8b18364fffce4c451e6f6fd218fa4ab646705 Timelineinfo 03/09/2026 CVE reserved 04/23/2026 +44 days Advisory disclosed 04/23/2026 +0 days VulDB entry created 04/23/2026 +0 days VulDB entry last update Sourcesinfo Vendor: kernel.org Advisory: git.kernel.org Status: Confirmed CVE: CVE-2026-31533 (🔒) GCVE (CVE): GCVE-0-2026-31533 GCVE (VulDB): GCVE-100-359162 Entryinfo Created: 04/23/2026 19:51 Changes: 04/23/2026 19:51 (59) Complete: 🔍 Cache ID: 99:6C7:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸