CVE-2024-43873

Severity CVSS v4.0:
Pending analysis
Type:
Unavailable / Other
Publication date:
21/08/2024
Last modified:
03/11/2025

Description

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

Vulnerable products and versions

CPE From Up to
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* 5.14 (including) 5.15.165 (excluding)
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* 5.16 (including) 6.1.103 (excluding)
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* 6.2 (including) 6.6.44 (excluding)
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* 6.7 (including) 6.10.3 (excluding)