CVE-2024-43873: vhost/vsock: always initialize seqpacket_allow
In the Linux kernel, the following vulnerability has been resolved:
vhost/vsock: always initialize seqpacketallow
There are two issues around seqpacketallow: 1. seqpacketallow is not initialized when socket is created. Thus if features are never set, it will be read uninitialized. 2. if VIRTIOVSOCKFSEQPACKET is set and then cleared, then seqpacketallow 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 seqpacketallow after allocation - set it unconditionally in setfeatures
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Configuration
Initialize seqpacket_allow after allocation, and set it unconditionally in set_features so it cannot remain uninitialized or uncleared when VIRTIO_VSOCK_F_SEQPACKET is cleared.
Linux kernel vhost/vsock seqpacket_allow = initialize after allocation and set unconditionally in set_features
Event History
Frequently Asked Questions
What is the severity of CVE-2024-43873?
CVE-2024-43873 is classified as a medium-severity vulnerability affecting the Linux kernel.
How do I fix CVE-2024-43873?
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.
Which Linux kernel versions are affected by CVE-2024-43873?
CVE-2024-43873 affects multiple Linux kernel versions ranging from 5.14 to 6.10.3.
What is the impact of CVE-2024-43873?
The impact of CVE-2024-43873 can lead to potential information disclosure due to uninitialized data being read from the socket.
Is CVE-2024-43873 fixed in the latest Linux kernel versions?
Yes, CVE-2024-43873 has been fixed in the latest stable Linux kernel releases.