CVE-2024-26800: tls: fix use-after-free on failed backlog decryption
First published: Thu Apr 04 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 crypto_aead_decrypt returns -EBUSY, tls_do_decryption will wait until all async decryptions have completed. If one of them fails, tls_do_decryption will return -EBADMSG and tls_decrypt_sg 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 tls_decrypt_done. The only true async case is when crypto_aead_decrypt returns -EINPROGRESS. With -EBUSY, we already waited so we can tell tls_sw_recvmsg that the data is available for immediate copy, but we need to notify tls_decrypt_sg (via the new ->async_done flag) that the memory has already been released.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=6.6.18<6.6.21 | |
| Linux Kernel | >=6.7.6<6.7.9 | |
| Linux Kernel | =6.8-rc1 | |
| Linux Kernel | =6.8-rc2 | |
| Linux Kernel | =6.8-rc3 | |
| Linux Kernel | =6.8-rc4 | |
| Linux Kernel | =6.8-rc5 | |
| Linux Kernel | =6.8-rc6 | |
| debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.135-1 6.12.22-1 6.12.25-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/13114dc5543069f7b97991e3b79937b6da05f5b0
- https://git.kernel.org/stable/c/1ac9fb84bc7ecd4bc6428118301d9d864d2a58d1
- https://git.kernel.org/stable/c/81be85353b0f5a7b660635634b655329b429eefe
- https://git.kernel.org/stable/c/f2b85a4cc763841843de693bbd7308fe9a2c4c89
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26800
- https://nvd.nist.gov/vuln/detail/CVE-2024-26800
- https://launchpad.net/bugs/cve/CVE-2024-26800
- https://security-tracker.debian.org/tracker/CVE-2024-26800
- https://ubuntu.com/security/CVE-2024-26800
- https://git.kernel.org/linus/13114dc5543069f7b97991e3b79937b6da05f5b0
Frequently Asked Questions
What is the severity of CVE-2024-26800?
CVE-2024-26800 is classified as a medium severity vulnerability in the Linux kernel.
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.
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.
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.
Has CVE-2024-26800 been officially resolved?
Yes, CVE-2024-26800 has been resolved in the Linux kernel with appropriate patches released.
- agent/weakness
- agent/title
- agent/first-publish-date
- agent/type
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/trending
- agent/severity
- agent/last-modified-date
- agent/remedy
- collector/usn-cve
- source/Ubuntu
- agent/description
- agent/event
- agent/source
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-api
- agent/tags
- agent/softwarecombine
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- version/linux kernel/6.6.18
- version/linux kernel/6.7.6
- version/linux kernel/6.8-rc1
- version/linux kernel/6.8-rc2
- version/linux kernel/6.8-rc3
- version/linux kernel/6.8-rc4
- version/linux kernel/6.8-rc5
- version/linux kernel/6.8-rc6
- package-manager/debian