Description
In the Linux kernel, the following vulnerability has been resolved: net: tls: handle backlogging of crypto requests Since we're setting the CRYPTO_TFM_REQ_MAY_BACKLOG flag on our requests to the crypto API, crypto_aead_{encrypt,decrypt} can return -EBUSY instead of -EINPROGRESS in valid situations. For example, when the cryptd queue for AESNI is full (easy to trigger with an artificially low cryptd.cryptd_max_cpu_qlen), requests will be enqueued to the backlog but still processed. In that case, the async callback will also be called twice: first with err == -EINPROGRESS, which it seems we can just ignore, then with err == 0. Compared to Sabrina's original patch this version uses the new tls_*crypt_async_wait() helpers and converts the EBUSY to EINPROGRESS to avoid having to modify all the error handling paths. The handling is identical.
Affected products
linux: linux kernel
References10
- git.kernel.org/stable/c/13eca403876bbea3716e82cdfe6f1e6febb38754 Patch
- git.kernel.org/stable/c/8590541473188741055d27b955db0777569438e3 Patch
- git.kernel.org/stable/c/ab6397f072e5097f267abf5cb08a8004e6b17694 Patch
- git.kernel.org/stable/c/cd1bbca03f3c1d845ce274c0d0a66de8e5929f72 Patch
- git.kernel.org/stable/c/13eca403876bbea3716e82cdfe6f1e6febb38754 Patch
- git.kernel.org/stable/c/8590541473188741055d27b955db0777569438e3 Patch
- git.kernel.org/stable/c/ab6397f072e5097f267abf5cb08a8004e6b17694 Patch
- git.kernel.org/stable/c/cd1bbca03f3c1d845ce274c0d0a66de8e5929f72 Patch
- git.kernel.org/stable/c/3ade391adc584f17b5570fd205de3ad029090368
- git.kernel.org/stable/c/3ade391adc584f17b5570fd205de3ad029090368
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 1% percentile: 55 · as of 5 November 2026
- CWE
- CWE-755
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.