First published: Fri May 10 2024(Updated: )
A flaw was found in QEMU in the Virtio PCI Bindings (hw/virtio/virtio-pci.c). An improper release and use of the irqfd for vector 0 during the boot process leads to a guest triggerable crash via vhost_net_stop(). The original patch [1] was found to be incomplete and is currently being reworked upstream [2][3]. [1] <a href="https://gitlab.com/qemu-project/qemu/-/commit/fcbb086ae590e910614fe5b8bf76e264f71ef304">https://gitlab.com/qemu-project/qemu/-/commit/fcbb086ae590e910614fe5b8bf76e264f71ef304</a> [2] <a href="https://gitlab.com/qemu-project/qemu/-/issues/2321">https://gitlab.com/qemu-project/qemu/-/issues/2321</a> [3] <a href="https://gitlab.com/qemu-project/qemu/-/issues/2334">https://gitlab.com/qemu-project/qemu/-/issues/2334</a>
Affected Software | Affected Version | How to fix |
---|---|---|
QEMU |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
REDHAT-BUG-2279965 is considered a critical vulnerability due to its potential to cause guest crashes.
To address REDHAT-BUG-2279965, apply the latest patch provided by the QEMU project when it becomes available.
REDHAT-BUG-2279965 specifically affects systems running QEMU with Virtio PCI Bindings.
Yes, REDHAT-BUG-2279965 can be exploited by a guest to trigger a crash in the host environment.
The vulnerability in REDHAT-BUG-2279965 is caused by improper handling of the irqfd for vector 0 during the QEMU boot process.