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

The following products are affected by CVE-2024-43873 vulnerability.

Here, you will find a curated list of external links that provide in-depth information to CVE-2024-43873.

URL	Resource
https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22
https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb
https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582
https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c
https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
https://lore.kernel.org/linux-cve-announce/2024082136-CVE-2024-43873-c547@gregkh/T
https://nvd.nist.gov/vuln/detail/CVE-2024-43873
https://www.cve.org/CVERecord?id=CVE-2024-43873