CVE-2024-4693: Qemu-kvm: virtio-pci: improper release of configure vector leads to guest triggerable crash

Published 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 vhostnetstop().

The original patch [1] was found to be incomplete and is currently being reworked upstream [2][3].

[1] https://gitlab.com/qemu-project/qemu/-/commit/fcbb086ae590e910614fe5b8bf76e264f71ef304 [2] https://gitlab.com/qemu-project/qemu/-/issues/2321 [3] https://gitlab.com/qemu-project/qemu/-/issues/2334

Other sources

A flaw was found in the QEMU 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 vhostnetstop(). This flaw allows a malicious guest to crash the QEMU process on the host.

Launchpad

Qemu-kvm: virtio-pci: improper release of configure vector leads to guest triggerable crash

Microsoft

Affected Software

2 affected componentsFixes available
debian/qemu
1:5.2+dfsg-11+deb11u31:5.2+dfsg-11+deb11u21:7.2+dfsg-7+deb12u121:9.2.2+ds-11:10.0.0~rc2+ds-2
Microsoft azl3 qemu 8.2.0-14

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/qemu to a version that resolves this vulnerability.

    Fixed in 1:5.2+dfsg-11+deb11u3Fixed in 1:5.2+dfsg-11+deb11u2Fixed in 1:7.2+dfsg-7+deb12u12Fixed in 1:9.2.2+ds-1Fixed in 1:10.0.0~rc2+ds-2

Event History

May 10, 2024
Data Sourced
via Red Hat·08:48 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·12:57 PM
Data Sourced
via MITRE·12:57 PM
DescriptionSeverityWeakness
May 14, 2024
Data Sourced
via NVD·03:44 PM
DescriptionSeverityWeakness
Nov 11, 2024
Data Sourced
via Launchpad·12:43 AM
Description
Nov 23, 2024
Data Sourced
via Ubuntu·12:44 AM
RemedyDescriptionSeverityAffected Software
May 6, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2024-4693?

CVE-2024-4693 is classified as a critical severity vulnerability due to the potential guest-triggered crash.

2

How do I fix CVE-2024-4693?

To resolve CVE-2024-4693, update QEMU to the latest patched version provided by your distribution.

3

What software is affected by CVE-2024-4693?

CVE-2024-4693 affects specific versions of QEMU in Debian, including versions 1:5.2+dfsg-11+deb11u3 and others.

4

What can happen if CVE-2024-4693 is exploited?

Exploitation of CVE-2024-4693 may lead to a denial of service condition by causing the QEMU guest to crash.

5

Is there a workaround for CVE-2024-4693?

Currently, there is no official workaround for CVE-2024-4693 other than applying the necessary software updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203