First published: Wed Feb 21 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: tls: fix race between async notify and socket close The submitting thread (one which called recvmsg/sendmsg) may exit as soon as the async crypto handler calls complete() so any code past that point risks touching already freed data. Try to avoid the locking and extra flags altogether. Have the main thread hold an extra reference, this way we can depend solely on the atomic ref counter for synchronization. Don't futz with reiniting the completion, either, we are now tightly controlling when completion fires.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/kernel | <6.8 | 6.8 |
Linux Kernel | >=5.7.0<6.1.79 | |
Linux Kernel | >=6.2.0<6.6.18 | |
Linux Kernel | >=6.7.0<6.7.6 | |
debian/linux | <=5.10.223-1<=5.10.226-1 | 6.1.123-1 6.1.119-1 6.12.11-1 6.12.12-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-26583 has not been assigned a specific CVSS score, but it is considered a significant vulnerability in the Linux kernel.
To remediate CVE-2024-26583, update the Linux kernel to version 6.8 or later for Red Hat systems, or apply the latest patches available in your Linux distribution.
CVE-2024-26583 affects Linux kernel versions from 5.7.0 up to 6.1.79 and between 6.2.0 and 6.6.18, as well as versions 6.7.0 to 6.7.6.
CVE-2024-26583 is classified as a local vulnerability, as it arises from operations that require local user privileges.
The impact of CVE-2024-26583 includes potential data corruption or system crashes if the vulnerable code is executed in the context of an application calling async crypto handlers.