Vulnerabilities · 2024 · Linux
CVE-2024-43873
Linux Kernel vulnerability
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
Affected products
Linux Kernel. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Linux Kernel runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 · Patch
- git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb · Patch
- git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582 · Patch
- git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c · Patch
- git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b · Patch
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- nvd.nist.gov/vuln/detail/CVE-2024-43873
- cve.org/CVERecord?id=CVE-2024-43873
More vulnerabilities in Linux products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.