CVE-2024-43873vhost/vsock: always initialize seqpacket_allow
- 7.8HighCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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
Timeline
ID reserved
By Linux
- 4 days later
· 4 days later
Published
- 21 months later
· 21 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected ced7b713711fdd8f99d8d04dc53451441d194c60 – < ea558f10fb05a6503c6e655a1b7d81fdf8e5924c
- affected ced7b713711fdd8f99d8d04dc53451441d194c60 – < 3062cb100787a9ddf45de30004b962035cd497fb
- affected ced7b713711fdd8f99d8d04dc53451441d194c60 – < 30bd4593669443ac58515e23557dc8cef70d8582
- affected ced7b713711fdd8f99d8d04dc53451441d194c60 – < eab96e8716cbfc2834b54f71cc9501ad4eec963b
- affected ced7b713711fdd8f99d8d04dc53451441d194c60 – < 1e1fdcbdde3b7663e5d8faeb2245b9b151417d22
- affected 5.14
- unaffected < 5.14
- unaffected 5.15.165 – ≤ 5.15.*
- unaffected 6.1.103 – ≤ 6.1.*
- unaffected 6.6.44 – ≤ 6.6.*
- unaffected 6.10.3 – ≤ 6.10.*
- unaffected 6.11 – ≤ *
References
References6
- https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c (opens in a new tab)
- https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb (opens in a new tab)
- https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582 (opens in a new tab)
- https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b (opens in a new tab)
- https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-40523 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-43873)Record last updated .