virtio-pci: Check if is_avq is NULL
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
virtio-pci: Check if is_avq is NULL
[bug] In the virtio_pci_common.c function vp_del_vqs, vp_dev->is_avq is involved to determine whether it is admin virtqueue, but this function vp_dev->is_avq may be empty. For installations, virtio_pci_legacy does not assign a value to vp_dev->is_avq.
[fix] Check whether it is vp_dev->is_avq before use.
[test] Test with virsh Attach device Before this patch, the following command would crash the guest system
After applying the patch, everything seems to be working fine.
From the CVE record · Linux
In the Linux kernel, virtio-pci can use an unset is_avq function pointer when deleting virtqueues. Attaching a device with virsh was observed to crash the guest before the fix; the input does not establish whether an attacker can trigger this remotely or what access they would need.
Operators of Linux guests using virtio-pci should check their kernel; affected versions are not specified.