First published: Wed Aug 21 2024(Updated: )
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
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=5.14<5.15.165 | |
Linux Kernel | >=5.16<6.1.103 | |
Linux Kernel | >=6.2<6.6.44 | |
Linux Kernel | >=6.7<6.10.3 | |
debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.11-1 6.12.12-1 | |
debian/linux-6.1 | 6.1.119-1~deb11u1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-43873 is classified as a medium-severity vulnerability affecting the Linux kernel.
To fix CVE-2024-43873, update your Linux kernel to a secure version, such as 5.10.223-1, 6.1.123-1, or any later release that addresses this vulnerability.
CVE-2024-43873 affects multiple Linux kernel versions ranging from 5.14 to 6.10.3.
The impact of CVE-2024-43873 can lead to potential information disclosure due to uninitialized data being read from the socket.
Yes, CVE-2024-43873 has been fixed in the latest stable Linux kernel releases.