Tracker / CVE-2024-43873
CVE-2024-43873
High 7.8
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 and versions
| linux | linux_kernel · 5.14 → 5.15.165 |
|---|---|
| linux | linux_kernel · 5.16 → 6.1.103 |
| linux | linux_kernel · 6.2 → 6.6.44 |
| linux | linux_kernel · 6.7 → 6.10.3 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.