CVE-2024-26583

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.

Dont futz with reiniting the completion, either, we are now tightly controlling when completion fires.

Weakness

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Software

Extended Description

A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:

A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Potential Mitigations

• Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
• Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/26.html
• https://cwe.mitre.org/data/definitions/29.html

References

• 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
• 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
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EZOU3745CWCDZ7EMKMXB2OEEIB5Q3IWM/