CVEvulnerability
CVE-2024-49864
4.7 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2024-10-21
- Last modified
- 2026-08-04
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.5 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CVSS 3.1 ([email protected])
- 4.7 MEDIUM — CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-362
Description
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix a race between socket set up and I/O thread creation
In rxrpc_open_socket(), it sets up the socket and then sets up the I/O
thread that will handle it. This is a problem, however, as there's a gap
between the two phases in which a packet may come into rxrpc_encap_rcv()
from the UDP packet but we oops when trying to wake the not-yet created I/O
thread.
As a quick fix, just make rxrpc_encap_rcv() discard the packet if there's
no I/O thread yet.
A better, but more intrusive fix would perhaps be to rearrange things such
that the socket creation is done by the I/O thread.
Affected configurations
• linux linux kernel (>= 6.2 <= 6.6.55)
• linux linux kernel (>= 6.10 < 6.10.14)
• linux linux kernel (>= 6.11 < 6.11.3)
• linux linux kernel 6.12
Related
Weakness · CWE (1)
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization weakness
References
- https://git.kernel.org/stable/c/56e415202b8a17de6496f4023e545fcb66f118ec Patch
- https://git.kernel.org/stable/c/bc212465326e8587325f520a052346f0b57360e6 Patch
- https://git.kernel.org/stable/c/c64f5fc95e9612fdf75587c8e21e494e614c18e2 Patch
- https://git.kernel.org/stable/c/cdf4bbbdb956d7426f687f38757ebca2a2759a0f Patch