CVE-2024-43873

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. CVE-2024-43873
In the Linux kernel, the following vulnerability has been resolved: vhost/vsock: always initialize seqpacket_allow There are two issues around seqpacket_allow: 1. seqpacket_allow is not initialized when socket is created. Thus if features are never set, it will be read uninitialized. 2. if VIRTIO_VSOCK_F_SEQPACKET is set and then cleared, then seqpacket_allow will not be cleared appropriately (existing apps I know about don't usually do this but it's legal and there's no way to be sure no one relies on this). To fix: - initialize seqpacket_allow after allocation - set it unconditionally in set_features

7.8 /10

CVSS v3 : HIGH

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 5.9

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 Patch
https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb Patch
https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582 Patch
https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c Patch
https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b Patch
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
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:*:*:*:*:*:*:*:*
History

03 Nov 2025, 22:18

Type Values Removed Values Added
References
  • () https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html -

03 Sep 2024, 13:35

Type Values Removed Values Added
First Time Linux linux Kernel
Linux
References () https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 - () https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 - Patch
References () https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb - () https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb - Patch
References () https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582 - () https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582 - Patch
References () https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c - () https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c - Patch
References () https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b - () https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b - Patch
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: vhost/vsock: inicializar siempre seqpacket_allow Hay dos problemas relacionados con seqpacket_allow: 1. seqpacket_allow no se inicializa cuando se crea el socket. Por lo tanto, si las funciones nunca se configuran, se leerá sin inicializar. 2. Si VIRTIO_VSOCK_F_SEQPACKET está configurado y luego borrado, entonces seqpacket_allow no se borrará apropiadamente (las aplicaciones existentes que conozco generalmente no hacen esto, pero es legal y no hay forma de estar seguro de que nadie confíe en esto). Para solucionarlo: - inicializar seqpacket_allow después de la asignación - configurarlo incondicionalmente en set_features
CWE CWE-909
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 7.8

21 Aug 2024, 01:15

Type Values Removed Values Added
New CVE
Information

Published : 2024-08-21 01:15

Updated : 2025-11-03 22:18

NVD link : CVE-2024-43873

Mitre link : CVE-2024-43873

CVE.ORG link : CVE-2024-43873

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-909

Missing Initialization of Resource