CVE-2024-26800: tls: fix use-after-free on failed backlog decryption

Published Apr 4, 2024
·
Updated

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

tls: fix use-after-free on failed backlog decryption

When the decrypt request goes to the backlog and cryptoaeaddecrypt returns -EBUSY, tlsdodecryption will wait until all async decryptions have completed. If one of them fails, tlsdodecryption will return -EBADMSG and tlsdecryptsg jumps to the error path, releasing all the pages. But the pages have been passed to the async callback, and have already been released by tlsdecryptdone.

The only true async case is when cryptoaeaddecrypt returns -EINPROGRESS. With -EBUSY, we already waited so we can tell tlsswrecvmsg that the data is available for immediate copy, but we need to notify tlsdecryptsg (via the new ->asyncdone flag) that the memory has already been released.

Affected Software

11 affected componentsFixes available
Linux Linux kernel>=6.6.18<6.6.21
Linux Linux kernel>=6.7.6<6.7.9
Linux Linux kernel=6.8-rc1
Linux Linux kernel=6.8-rc2
Linux Linux kernel=6.8-rc3
Linux Linux kernel=6.8-rc4
Linux Linux kernel=6.8-rc5
Linux Linux kernel=6.8-rc6
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
Linux Linux kernel>=5.15.160<5.16
Microsoft cbl2 kernel 5.15.186.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1

Event History

Apr 4, 2024
CVE Published
via MITRE·08:20 AM
Data Sourced
via MITRE·08:20 AM
DescriptionSeverity
Data Sourced
via NVD·09:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 31, 2024
Data Sourced
via Launchpad·04:20 PM
Description
Apr 27, 2025
Data Sourced
via Ubuntu·12:14 AM
RemedyDescriptionSeverityAffected Software
May 13, 2025
Data Sourced
via Debian·12:18 AM
DescriptionAffected Software
Dec 12, 2025
Data Sourced
via Microsoft·01:02 AM
DescriptionSeverityWeaknessAffected Software
Dec 25, 58560
Event
via MITRE·02:01 AM

Frequently Asked Questions

1

What is the severity of CVE-2024-26800?

CVE-2024-26800 is classified as a medium severity vulnerability in the Linux kernel.

2

How do I fix CVE-2024-26800?

To fix CVE-2024-26800, users should update to the patched versions of the Linux kernel as specified in the security advisories.

3

Which versions of the Linux kernel are affected by CVE-2024-26800?

CVE-2024-26800 affects Linux kernel versions 6.6.18 to 6.6.21, 6.7.6 to 6.7.9, and specific 6.8 release candidates.

4

What type of vulnerability is CVE-2024-26800?

CVE-2024-26800 is a use-after-free vulnerability occurring during failed backlog decryption in the TLS protocol within the Linux kernel.

5

Has CVE-2024-26800 been officially resolved?

Yes, CVE-2024-26800 has been resolved in the Linux kernel with appropriate patches released.

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