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

> A malicious guest can crash the QEMU host process by triggering an improper release of the configure vector during boot.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 May 2024
- **Updated:** 8 Nov 2025
- **Also known as:** AZL-60919, BELL-CVE-2024-4693, DEBIAN-CVE-2024-4693, GHSA-c58x-2x8h-gwq3, UBUNTU-CVE-2024-4693

## What is CVE-2024-4693?

CVE-2024-4693 is a medium-severity denial of service vulnerability in Red Hat Enterprise Linux 6, published on 10 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-672 (Operation on a Resource after Expiration or Release)

## Which versions are affected by CVE-2024-4693?


## How do I fix CVE-2024-4693?

Apply the vendor's patch.

## Is CVE-2024-4693 being exploited?

There is no known exploitation of CVE-2024-4693 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4693 and fix it if it is affected.

What it is: CVE-2024-4693 is a medium-severity denial of service vulnerability in Red Hat Enterprise Linux 6, published on 10 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4693 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-4693/ (Markdown: https://insights.sbomify.com/CVE-2024-4693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4693
- OSV: https://osv.dev/vulnerability/CVE-2024-4693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-4693/
Summaries are generated and may contain mistakes; the official description above is the record.