# CVE-2023-2680: Dma reentrancy issue (incomplete fix for cve-2021-3750)

> An incomplete fix for a DMA reentrancy issue in QEMU allows attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Sep 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-69cm-qhp7-ch23, MINI-48mc-pjgf-fvrh, MINI-8r8q-wjr6-rrvj, MINI-r83g-3pf5-8r24, RHSA-2023:6368

## What is CVE-2023-2680?

CVE-2023-2680 is a high-severity use after free vulnerability in Qemu Qemu, published on 13 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This CVE exists because of an incomplete fix for CVE-2021-3750. More specifically, the qemu-kvm package as released for Red Hat Enterprise Linux 9.1 via RHSA-2022:7967 included a version of qemu-kvm that was actually missing the fix for CVE-2021-3750.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2023-2680?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `qemu-guest-agent` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-guest-agent-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-img` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-img-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-audio-dbus-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-audio-pa` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-audio-pa-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-block-blkio` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-block-blkio-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-block-curl` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-block-curl-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-block-rbd` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-block-rbd-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-common` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-common-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-core` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-core-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-display-virtio-gpu` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-display-virtio-gpu-ccw` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-display-virtio-gpu-ccw-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-display-virtio-gpu-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-display-virtio-gpu-pci` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-display-virtio-gpu-pci-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-display-virtio-vga` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-display-virtio-vga-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-usb-host` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-usb-host-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-usb-redirect` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-device-usb-redirect-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-docs` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-tests-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-tools` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-tools-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-ui-dbus-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-ui-egl-headless` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-ui-egl-headless-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |
| `qemu-kvm-ui-opengl` | Red Hat:enterprise_linux:9::appstream | All versions | 17:8.0.0-16.el9_3 |

Products: Qemu Qemu, Redhat Enterprise Linux.

## How do I fix CVE-2023-2680?

Apply the vendor's patch.

## Is CVE-2023-2680 being exploited?

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

## Other vulnerabilities in Qemu Qemu

- [CVE-2022-36648](https://insights.sbomify.com/CVE-2022-36648/): Null dereference in n/a (critical 10.0)
- [CVE-2015-8556](https://insights.sbomify.com/CVE-2015-8556/): Race condition in n/a (critical 10.0)
- [CVE-2009-3616](https://insights.sbomify.com/CVE-2009-3616/): Use after free in n/a (critical 9.9)
- [CVE-2019-12928](https://insights.sbomify.com/CVE-2019-12928/): Command injection in n/a (critical 9.8)
- [CVE-2019-12929](https://insights.sbomify.com/CVE-2019-12929/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2680 and fix it if it is affected.

What it is: CVE-2023-2680 is a high-severity use after free vulnerability in Qemu Qemu, published on 13 Sep 2023. 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-2023-2680 in the wild and no public exploit code.

Affected product: Qemu Qemu. 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-2023-2680/ (Markdown: https://insights.sbomify.com/CVE-2023-2680/index.md)
```

## Sources

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

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