CVE-2022-49814

  1. Yack CVE
  2. Vulnerabilities (CVE)
  3. CVE-2022-49814

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: kcm: close race conditions on sk_receive_queue sk->sk_receive_queue is protected by skb queue lock, but for KCM sockets its RX path takes mux->rx_lock to protect more than just skb queue. However, kcm_recvmsg() still only grabs the skb queue lock, so race conditions still exist. We can teach kcm_recvmsg() to grab mux->rx_lock too but this would introduce a potential performance regression as struct kcm_mux can be shared by multiple KCM sockets. So we have to enforce skb queue lock in requeue_rx_msgs() and handle skb peek case carefully in kcm_wait_data(). Fortunately, skb_recv_datagram() already handles it nicely and is widely used by other sockets, we can just switch to skb_recv_datagram() after getting rid of the unnecessary sock lock in kcm_recvmsg() and kcm_splice_read(). Side note: SOCK_DONE is not used by KCM sockets, so it is safe to get rid of this check too. I ran the original syzbot reproducer for 30 min without seeing any issue.

References
Link Resource
https://git.kernel.org/stable/c/22f6b5d47396b4287662668ee3f5c1f766cb4259 Patch
https://git.kernel.org/stable/c/4154b6afa2bd639214ff259d912faad984f7413a Patch
https://git.kernel.org/stable/c/5121197ecc5db58c07da95eb1ff82b98b121a221 Patch
https://git.kernel.org/stable/c/bf92e54597d842da127c59833b365d6faeeaf020 Patch
https://git.kernel.org/stable/c/ce57d6474ae999a3b2d442314087473a646a65c7 Patch
https://git.kernel.org/stable/c/d9ad4de92e184b19bcae4da10dac0275abf83931 Patch
https://git.kernel.org/stable/c/f7b0e95071bb4be4b811af3f0bfc3e200eedeaa3 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:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc5:*:*:*:*:*:*
History

07 Nov 2025, 18:51

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/22f6b5d47396b4287662668ee3f5c1f766cb4259 - () https://git.kernel.org/stable/c/22f6b5d47396b4287662668ee3f5c1f766cb4259 - Patch
References () https://git.kernel.org/stable/c/4154b6afa2bd639214ff259d912faad984f7413a - () https://git.kernel.org/stable/c/4154b6afa2bd639214ff259d912faad984f7413a - Patch
References () https://git.kernel.org/stable/c/5121197ecc5db58c07da95eb1ff82b98b121a221 - () https://git.kernel.org/stable/c/5121197ecc5db58c07da95eb1ff82b98b121a221 - Patch
References () https://git.kernel.org/stable/c/bf92e54597d842da127c59833b365d6faeeaf020 - () https://git.kernel.org/stable/c/bf92e54597d842da127c59833b365d6faeeaf020 - Patch
References () https://git.kernel.org/stable/c/ce57d6474ae999a3b2d442314087473a646a65c7 - () https://git.kernel.org/stable/c/ce57d6474ae999a3b2d442314087473a646a65c7 - Patch
References () https://git.kernel.org/stable/c/d9ad4de92e184b19bcae4da10dac0275abf83931 - () https://git.kernel.org/stable/c/d9ad4de92e184b19bcae4da10dac0275abf83931 - Patch
References () https://git.kernel.org/stable/c/f7b0e95071bb4be4b811af3f0bfc3e200eedeaa3 - () https://git.kernel.org/stable/c/f7b0e95071bb4be4b811af3f0bfc3e200eedeaa3 - Patch
First Time Linux linux Kernel
Linux
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 4.7
CPE cpe:2.3:o:linux:linux_kernel:6.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc4:*:*:*:*:*:*
CWE CWE-362

02 May 2025, 13:53

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: kcm: condiciones de ejecución cerradas en sk_receive_queue. sk->sk_receive_queue está protegido por el bloqueo de cola skb, pero para los sockets KCM su ruta RX toma mux->rx_lock para proteger más que solo la cola skb. Sin embargo, kcm_recvmsg() todavía solo captura el bloqueo de cola skb, por lo que las condiciones de ejecución aún existen. Podemos enseñar a kcm_recvmsg() a capturar también mux->rx_lock, pero esto introduciría una posible regresión del rendimiento, ya que la estructura kcm_mux puede ser compartida por varios sockets KCM. Por lo tanto, debemos aplicar el bloqueo de cola skb en requeue_rx_msgs() y manejar el caso de skb peek con cuidado en kcm_wait_data(). Afortunadamente, skb_recv_datagram() ya lo gestiona correctamente y es ampliamente utilizado por otros sockets. Podemos cambiar a skb_recv_datagram() tras eliminar el bloqueo de sock innecesario en kcm_recvmsg() y kcm_splice_read(). Nota: Los sockets KCM no utilizan SOCK_DONE, por lo que también es seguro omitir esta comprobación. Ejecuté el reproductor syzbot original durante 30 minutos sin observar ningún problema.

01 May 2025, 15:16

Type Values Removed Values Added
New CVE
Information

Published : 2025-05-01 15:16

Updated : 2025-11-07 18:51

NVD link : CVE-2022-49814

Mitre link : CVE-2022-49814

CVE.ORG link : CVE-2022-49814

JSON object : View

Products Affected

linux

CWE
CWE-362

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