Race Condition Affecting kernel-cross-headers package, versions <0:4.18.0-553.8.1.el8_10

Note: Versions mentioned in the description apply only to the upstream kernel-cross-headers package and not the kernel-cross-headers package as distributed by Centos. See How to fix? for Centos:8 relevant fixed versions and status.

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.

• https://access.redhat.com/security/cve/CVE-2024-26583
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EZOU3745CWCDZ7EMKMXB2OEEIB5Q3IWM/
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OX4EWCYDZRTOEMC2C6OF7ZACAP23SUB5/
• https://git.kernel.org/stable/c/6209319b2efdd8524691187ee99c40637558fa33
• https://git.kernel.org/stable/c/7a3ca06d04d589deec81f56229a9a9d62352ce01
• https://git.kernel.org/stable/c/86dc27ee36f558fe223dbdfbfcb6856247356f4a
• https://git.kernel.org/stable/c/aec7961916f3f9e88766e2688992da6980f11b8d
• https://git.kernel.org/stable/c/f17d21ea73918ace8afb9c2d8e734dbf71c2c9d7