vhost/vsock: always initialize seqpacket_allow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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
From the CVE record · Linux
The Linux kernel’s vhost/vsock component can read seqpacket_allow before it is initialized if socket features are never set. The setting can also remain enabled after VIRTIO_VSOCK_F_SEQPACKET is cleared. The input does not specify an attacker capability or whether exploitation requires network access, authentication, or user interaction.
Teams running the Linux kernel should check their versions for this vulnerability; affected versions are not specified.