What’s Vulnerable › Vulnerabilities

CVE-2024-43873: vhost/vsock: always initialize seqpacket_allow

• Severity: high (CVSS 7.8 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2024-08-21 · updated 2026-06-17
• Weakness: CWE-909

Description

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: from 5.14 before 5.15.165; from 5.16 before 6.1.103; from 6.2 before 6.6.44; from 6.7 before 6.10.3 — fixed in 5.15.165, 6.1.103, 6.10.3, 6.6.44

How to fix

Upgrade to a fixed version: Linux kernel 5.15.165, 6.1.103, 6.10.3, 6.6.44. Check the vendor advisory for mitigations.

References

• 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

Get alerted when CVE-2024-43873 or the next vulnerability affects your stack