Vulnerability in Linux
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
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.002 (11.2th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 11th percentile — 11.2% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.002 · newest: 0.002 · change: 0.000
Affected products
- Linux — versions ced7b713711fdd8f99d8d04dc53451441d194c60, 5.14, 0
- Linux Kernel
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2024-43873?
- CVE-2024-43873 is a high-severity vulnerability in Linux, classified under CWE-909. CVSS score: 7.8/10. Published 2024-08-21.
- How severe is CVE-2024-43873?
- High severity. CVSS v3 base score is 7.8 out of 10.