vhost/vsock: always initialize seqpacket_allow
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1e1fdcbdde3b7663e5d8faeb2245b9b151417d22, Kernel 3062cb100787a9ddf45de30004b962035cd497fb, Kernel 30bd4593669443ac58515e23557dc8cef70d8582 and 2 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.14, >=ced7b713711fdd8f99d8d04dc53451441d194c60 <1e1fdcbdde3b7663e5d8faeb2245b9b151417d22, >=ced7b713711fdd8f99d8d04dc53451441d194c60 <3062cb100787a9ddf45de30004b962035cd497fb, >=ced7b713711fdd8f99d8d04dc53451441d194c60 <30bd4593669443ac58515e23557dc8cef70d8582, >=ced7b713711fdd8f99d8d04dc53451441d194c60 <ea558f10fb05a6503c6e655a1b7d81fdf8e5924c, >=ced7b713711fdd8f99d8d04dc53451441d194c60 <eab96e8716cbfc2834b54f71cc9501ad4eec963b | 1e1fdcbdde3b7663e5d8faeb2245b9b151417d22, 3062cb100787a9ddf45de30004b962035cd497fb, 30bd4593669443ac58515e23557dc8cef70d8582, ea558f10fb05a6503c6e655a1b7d81fdf8e5924c, eab96e8716cbfc2834b54f71cc9501ad4eec963b |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket