Skip to main content
VulnerabilityPublished Updated

CVE-2024-4693: CWE-672

Source GCVE Database

0
Compare
Authoritative record:CVE-2024-4693· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 5 Nov 2026, 16:04 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.15.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 May 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Enterprise Linux 6qemu-kvmAffected–Fixed in–
Red Hat Enterprise Linux 7qemu-kvmAffected–Fixed in–
Red Hat Enterprise Linux 7qemu-kvm-maAffected–Fixed in–
Red Hat Enterprise Linux 8virt:rhel/qemu-kvmAffected–Fixed in–
Red Hat Enterprise Linux 8 Advanced Virtualizationvirt:av/qemu-kvmAffected–Fixed in–
Red Hat Enterprise Linux 9qemu-kvmAffected–Fixed in–

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.

References

Community reviews

Loading reviews…