Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Critical

Linux kernel net/tls use-after-free in tls_do_encryption() -EBUSY error path

IdentifiersCVE-2026-31533CWE-416· Use After Free

CVE-2026-31533 is a use-after-free vulnerability in the Linux kernel net/tls subsystem, specifically in the -EBUSY error path of tls_do_encryption(). The bug was introduced by commit 859054147318 ("net: tls: handle backlogging of crypto requests"). When crypto_aead_encrypt() returns -EBUSY, the encryption request is queued to the cryptd backlog and later completed asynchronously via tls_encrypt_done(). That callback restores the scatterlist entry fields (sge->offset and sge->length) and decrements ctx->encrypt_pending. If tls_encrypt_async_wait() subsequently returns an error, the synchronous error path in tls_do_encryption() performs the same cleanup a second time, causing double restoration of the scatterlist state and a double-decrement of ctx->encrypt_pending. Because encrypt_pending is used as a sentinel initialized to 1, the double-decrement corrupts the pending-operation state and can cause future waits for asynchronous callbacks to be skipped. A subsequent sendmsg path can then free the tls_rec via bpf_exec_tx_verdict() while a cryptd callback is still outstanding, leading to a use-after-free when the callback later executes against the freed record.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in kernel memory corruption through a use-after-free on a freed tls_rec object in the TLS transmit path. Because the flaw occurs in kernel context and affects object lifetime tracking around asynchronous crypto completion, impact can include kernel crash or denial of service, and potentially arbitrary code execution in kernel context depending on exploitability and target environment. The supplied context also states the issue was reportedly exploited as a zero-day on lts-6.12.77 and cos-121-18867.381.30.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by minimizing use of the affected kernel TLS transmit path in environments where asynchronous crypto backlogging can occur. Limit untrusted network-triggerable access to services relying on kernel TLS offload, and avoid configurations that combine the vulnerable net/tls path with BPF-based TX verdict handling where feasible. Because this is a kernel memory-safety flaw in core networking code, mitigation is incomplete without upgrading to a fixed kernel.

Remediation

Patch, then assume compromise.

Apply a kernel update containing the upstream fix for CVE-2026-31533. The fix changes tls_do_encryption() so that when the -EBUSY asynchronous wait path returns an error, the synchronous path does not repeat cleanup already performed by tls_encrypt_done(). This prevents double decrement of ctx->encrypt_pending and duplicate scatterlist restoration. Vendor-fixed package versions in the provided context include, for example, SUSE kernel-default >= 5.14.21-150500.55.166.1 for several SLES 15 SP5 lines, >= 6.4.0-150600.23.112.1 for several SLES 15 SP6 lines, and other branch-specific fixed builds as listed by the vendor. Reboot after installing the updated kernel.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.