CVE-2024-49864

  1. Yack CVE
  2. Vulnerabilities (CVE)
  3. CVE-2024-49864

4.7 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.0 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity HIGH

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

I

n 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.

References
Link Resource
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
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
History

13 Nov 2024, 14:23

Type Values Removed Values Added
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 4.7
CWE CWE-362
References () https://git.kernel.org/stable/c/56e415202b8a17de6496f4023e545fcb66f118ec - () https://git.kernel.org/stable/c/56e415202b8a17de6496f4023e545fcb66f118ec - Patch
References () https://git.kernel.org/stable/c/bc212465326e8587325f520a052346f0b57360e6 - () https://git.kernel.org/stable/c/bc212465326e8587325f520a052346f0b57360e6 - Patch
References () https://git.kernel.org/stable/c/c64f5fc95e9612fdf75587c8e21e494e614c18e2 - () https://git.kernel.org/stable/c/c64f5fc95e9612fdf75587c8e21e494e614c18e2 - Patch
References () https://git.kernel.org/stable/c/cdf4bbbdb956d7426f687f38757ebca2a2759a0f - () https://git.kernel.org/stable/c/cdf4bbbdb956d7426f687f38757ebca2a2759a0f - Patch
First Time Linux
Linux linux Kernel
CPE cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*

23 Oct 2024, 15:13

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: rxrpc: Corrige una ejecución entre la configuración del socket y la creación del hilo de E/S En rxrpc_open_socket(), configura el socket y luego configura el hilo de E/S que lo manejará. Sin embargo, esto es un problema, ya que hay una brecha entre las dos fases en las que un paquete puede llegar a rxrpc_encap_rcv() desde el paquete UDP, pero fallo al intentar despertar el hilo de E/S aún no creado. Como solución rápida, simplemente haga que rxrpc_encap_rcv() descarte el paquete si aún no hay un hilo de E/S. Una solución mejor, pero más intrusiva, tal vez sería reorganizar las cosas de modo que la creación del socket la realice el hilo de E/S.

21 Oct 2024, 18:15

Type Values Removed Values Added
New CVE
Information

Published : 2024-10-21 18:15

Updated : 2024-11-13 14:23

NVD link : CVE-2024-49864

Mitre link : CVE-2024-49864

CVE.ORG link : CVE-2024-49864

JSON object : View

Products Affected

linux

CWE
CWE-362

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')