CVE-2024-26584

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2024-26584
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-26584.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2024-26584
Downstream
Related
Published
2024-02-21T14:59:12.452Z
Modified
2026-03-14T12:29:50.144333Z
Summary
net: tls: handle backlogging of crypto requests
Details

In the Linux kernel, the following vulnerability has been resolved:

net: tls: handle backlogging of crypto requests

Since we're setting the CRYPTOTFMREQMAYBACKLOG flag on our requests to the crypto API, cryptoaead{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.cryptdmaxcpu_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_*cryptasyncwait() helpers and converts the EBUSY to EINPROGRESS to avoid having to modify all the error handling paths. The handling is identical.

Database specific 
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/26xxx/CVE-2024-26584.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
a54667f6728c2714a400f3c884727da74b6d1717
Fixed
3ade391adc584f17b5570fd205de3ad029090368
Fixed
cd1bbca03f3c1d845ce274c0d0a66de8e5929f72
Fixed
13eca403876bbea3716e82cdfe6f1e6febb38754
Fixed
ab6397f072e5097f267abf5cb08a8004e6b17694
Fixed
8590541473188741055d27b955db0777569438e3

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-26584.json"