CVE-2024-26583
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.
Affected Packages
Platform | Package | Release Date | Advisory | Status |
---|---|---|---|---|
Amazon Linux 1 | kernel | Not Affected | ||
Amazon Linux 2 - Core | kernel | Not Affected | ||
Amazon Linux 2 - Kernel-5.10 Extra | kernel | 2024-05-09 | ALAS2KERNEL-5.10-2024-057 | Fixed |
Amazon Linux 2 - Kernel-5.15 Extra | kernel | 2024-05-09 | ALAS2KERNEL-5.15-2024-043 | Fixed |
Amazon Linux 2 - Kernel-5.4 Extra | kernel | 2024-05-09 | ALAS2KERNEL-5.4-2024-065 | Fixed |
Amazon Linux 2023 | kernel | 2024-02-29 | ALAS2023-2024-549 | Fixed |
CVSS Scores
Score Type | Score | Vector | |
---|---|---|---|
Amazon Linux | CVSSv3 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
NVD | CVSSv3 | 4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |