Menu

Star on GitHub · 3.2k

CVE-2026-31533

9.8 · CRITICAL

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…

Published Apr 23, 2026CWE-416EPSS 0.73%

Overview

CVE-2026-31533 is a critical-severity vulnerability. It was published on April 23, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-31533?

CVE-2026-31533 is a critical-severity vulnerability. It was published on April 23, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

How severe is CVE-2026-31533?

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-31533?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31533?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31533 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2026

View all