# CVE-2022-2962: Denial of service in QEMU

> A malicious guest can crash the QEMU host process via a DMA reentrancy flaw in Tulip device emulation, causing denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 13 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** AZL-10975, AZL-35159, DEBIAN-CVE-2022-2962, GHSA-wmwv-5vwp-c54w, openSUSE-SU-2024:12393-1

## What is CVE-2022-2962?

CVE-2022-2962 is a high-severity denial of service vulnerability in Qemu Qemu, published on 13 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn't check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly leading to a stack or heap overflow. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.

Weakness: CWE-662 (Improper Synchronization), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2022-2962?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `qemu` | openSUSE:Tumbleweed | All versions | 7.1.0-2.1 |

Products: Qemu Qemu.

## How do I fix CVE-2022-2962?

Apply the vendor's patch.

## Is CVE-2022-2962 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2962 exists.

## 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-2022-2962 and fix it if it is affected.

What it is: CVE-2022-2962 is a high-severity denial of service vulnerability in Qemu Qemu, published on 13 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2962 exists.

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-2022-2962/ (Markdown: https://insights.sbomify.com/CVE-2022-2962/index.md)
```

## Sources

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

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