CVE-2024-26584: net: tls: handle backlogging of crypto requests

Published Feb 21, 2024
·
Updated

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.cryptdmaxcpuqlen), 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 tlscryptasyncwait() helpers and converts the EBUSY to EINPROGRESS to avoid having to modify all the error handling paths. The handling is identical.

Other sources

Linux Kernel is vulnerable to a denial of service, caused by a flaw when setting the CRYPTOTFMREQMAYBACKLOG flag on requests to the crypto API in the tls subsystem. By sending a specially crafted request, a local authenticated attacker could exploit this vulnerability to cause a denial of service condition.

IBM

Affected Software

12 affected componentsFixes available
Linux Linux kernel>=4.16.0<6.1.84
Linux Linux kernel>=6.2.0<6.6.18
Linux Linux kernel>=6.7.0<6.7.6
IBM Security Verify Governance<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager Software Stack<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager Virtual Appliance<=ISVG 10.0.2
IBM Security Verify Governance Identity Manager Container<=ISVG 10.0.2
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.25-16.12.27-1
redhat/kernel<6.8
6.8
Microsoft cbl2 kernel 5.15.180.1-1
Microsoft cbl2 kernel 5.15.158.2-1
Microsoft cbl2 kernel 5.15.180.1-1

Event History

Feb 21, 2024
CVE Published
via MITRE·02:59 PM
Data Sourced
via MITRE·02:59 PM
Description
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 22, 2024
Data Sourced
via Red Hat·02:29 PM
DescriptionSeverityAffected Software
May 1, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Jun 8, 2024
Data Sourced
via Launchpad·01:04 AM
Description
Apr 28, 2025
Data Sourced
via Ubuntu·02:16 PM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-26584?

CVE-2024-26584 has been categorized as a high-severity vulnerability due to potential impact on cryptographic operations.

2

How do I fix CVE-2024-26584?

To mitigate CVE-2024-26584, update your Linux kernel to version 6.8 or any recommended patched version listed by your distribution.

3

What software is affected by CVE-2024-26584?

CVE-2024-26584 affects various versions of the Linux kernel, particularly versions 4.16.0 to 6.7.6 and 6.2.0 to 6.6.18.

4

Is CVE-2024-26584 remotely exploitable?

CVE-2024-26584 is not considered remotely exploitable, as it requires local access to exploit the vulnerability.

5

What type of vulnerability is CVE-2024-26584?

CVE-2024-26584 is classified as a vulnerability related to cryptographic request handling in the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203