https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:38:03 +0000 https://cve.radiocsirt.org/vuln/cve-2024-43873 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>vhost/vsock: always initialize seqpacket_allow</p> <p>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&#39;t usually do this but it&#39;s legal and there&#39;s no way to be sure no one relies on this).</p> <p>To fix: - initialize seqpacket_allow after allocation - set it unconditionally in set_features</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>vhost/vsock: always initialize seqpacket_allow</p> <p>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&#39;t usually do this but it&#39;s legal and there&#39;s no way to be sure no one relies on this).</p> <p>To fix: - initialize seqpacket_allow after allocation - set it unconditionally in set_features</p> https://cve.radiocsirt.org/vuln/cve-2024-43873