CVE-2026-31533·Kernel vulnerability
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.
- Severity
- critical
- Software
- Kernel
- Fixed in
- 6.19.13
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.71% — higher than 52% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-31533 scores 9.8 on CVSS, so a successful attack would be serious — but at 0.71%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 6.19.13
Fixed in: 6.19.13
How to fix this CVE
Update your Linux kernel to version 6.19.13 or later to patch a critical use-after-free vulnerability in the TLS encryption code path. This issue affects kernel versions 6.19 through 6.19.12 and can lead to memory corruption and potential system crashes when TLS async encryption requests encounter backlog conditions. Prioritize this update for systems using TLS/DTLS protocols with cryptographic acceleration.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version with `uname -r` and verify it is 6.19.13 or later
- Step 2: Confirm TLS functionality is enabled in your kernel config with `grep -i tls /boot/config-$(uname -r)` (should show CONFIG_TLS=m or CONFIG_TLS=y)
- Step 3: Search system logs for use-after-free warnings related to TLS with `sudo dmesg | grep -i 'use-after-free\|tls\|encrypt_pending'`
- Step 4: After applying the kernel update, reboot and run `uname -r` again to confirm the new version is loaded, then verify TLS module loads without errors using `lsmod | grep tls`
FAQ
What is CVE-2026-31533?
CVE-2026-31533 is a critical use-after-free vulnerability in the Linux kernel's TLS implementation where async encryption error handling performs redundant cleanup of cryptographic request metadata, leading to memory corruption and potential kernel panic or information disclosure.
Is CVE-2026-31533 being actively exploited?
No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are available, though the critical CVSS score and memory safety implications warrant immediate patching.
What versions of Kernel are affected by CVE-2026-31533?
Linux kernel versions 6.19 through 6.19.12 are affected; version 6.19.13 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-31533?
Run `uname -r` to display your kernel version—if it shows 6.19.x where x is less than 13, your system is vulnerable and requires an immediate kernel update.
Does Defensia detect CVE-2026-31533?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-31533 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/02f3ecadb23558bbe068e6504118f1b712d4ece0
- https://git.kernel.org/stable/c/0e43e0a3c94044acc74b8e0927c27972eb5a59e8
- https://git.kernel.org/stable/c/2694d408b0e595024e0fc1d64ff9db0358580f74
- https://git.kernel.org/stable/c/414fc5e5a5aff776c150f1b86770e0a25a35df3a
- https://git.kernel.org/stable/c/5d70eb25b41e9b010828cd12818b06a0c3b04412
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-31533. Free for 1 server.
Get started free