Bug 1222728 (CVE-2024-26800) - VUL-0: CVE-2024-26800: kernel: tls: use-after-free on failed backlog decryption
Summary: VUL-0: CVE-2024-26800: kernel: tls: use-after-free on failed backlog decryption
Status: RESOLVED FIXED
Alias: CVE-2024-26800
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/400352/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-12 12:27 UTC by SMASH SMASH
Modified: 2024-07-01 16:09 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-04-12 12:27:08 UTC
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-26800
https://www.cve.org/CVERecord?id=CVE-2024-26800
https://git.kernel.org/stable/c/1ac9fb84bc7ecd4bc6428118301d9d864d2a58d1
https://git.kernel.org/stable/c/81be85353b0f5a7b660635634b655329b429eefe
https://git.kernel.org/stable/c/13114dc5543069f7b97991e3b79937b6da05f5b0
https://git.kernel.org/stable/c/f2b85a4cc763841843de693bbd7308fe9a2c4c89
https://bugzilla.redhat.com/show_bug.cgi?id=2273472
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-26800.mbox
Comment 1 Thomas Leroy 2024-04-12 12:28:20 UTC
SLE15-SP6-GA and stable have both offending and fixing commit, and no other branch is affected.
Only a changelog update needed
Comment 2 Oscar Salvador 2024-04-17 03:31:11 UTC
References updated.
Back to sec-team.
Comment 13 Andrea Mattiazzo 2024-06-05 12:59:53 UTC
All done, closing.