CVE-2024-26584
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.7% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.7% in the next 30 days (EPSS).
- Severity: 9.8 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.7% · EPSS, next 30 days
- Weakness
- CWE-755
- Record status
- Modified
Affected
- Linux Kernel < 6.1.84
- Linux Kernel < 6.6.18
- Linux Kernel < 6.7.6
Attack profile CVSS 3.1 · 9.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-26584.md and follow it. Check whether this project is affected by CVE-2024-26584. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/13eca403876bbea3716e82cdfe6f1e6febb38754
- https://git.kernel.org/stable/c/8590541473188741055d27b955db0777569438e3
- https://git.kernel.org/stable/c/ab6397f072e5097f267abf5cb08a8004e6b17694
- https://git.kernel.org/stable/c/cd1bbca03f3c1d845ce274c0d0a66de8e5929f72
- https://git.kernel.org/stable/c/13eca403876bbea3716e82cdfe6f1e6febb38754
- https://git.kernel.org/stable/c/8590541473188741055d27b955db0777569438e3
- https://git.kernel.org/stable/c/ab6397f072e5097f267abf5cb08a8004e6b17694
- https://git.kernel.org/stable/c/cd1bbca03f3c1d845ce274c0d0a66de8e5929f72
References
- https://git.kernel.org/stable/c/13eca403876bbea3716e82cdfe6f1e6febb38754
- https://git.kernel.org/stable/c/3ade391adc584f17b5570fd205de3ad029090368
- https://git.kernel.org/stable/c/8590541473188741055d27b955db0777569438e3
- https://git.kernel.org/stable/c/ab6397f072e5097f267abf5cb08a8004e6b17694
- https://git.kernel.org/stable/c/cd1bbca03f3c1d845ce274c0d0a66de8e5929f72
- https://git.kernel.org/stable/c/13eca403876bbea3716e82cdfe6f1e6febb38754
- https://git.kernel.org/stable/c/3ade391adc584f17b5570fd205de3ad029090368
- https://git.kernel.org/stable/c/8590541473188741055d27b955db0777569438e3
- https://git.kernel.org/stable/c/ab6397f072e5097f267abf5cb08a8004e6b17694
- https://git.kernel.org/stable/c/cd1bbca03f3c1d845ce274c0d0a66de8e5929f72
- https://lists.fedoraproject.org/archives/list/[email protected]/message/EZOU3745CWCDZ7EMKMXB2OEEIB5Q3IWM/