# CVE-2022-3872: An off-by-one read/write issue was found in the SDHCI device of QEMU.


- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 7 Nov 2022
- **Updated:** 5 May 2025
- **Also known as:** AZL-11441, AZL-35163, DEBIAN-CVE-2022-3872, ECHO-6871-872a-d66e, GHSA-px5j-xw79-w7p8, UBUNTU-CVE-2022-3872

## What is CVE-2022-3872?

CVE-2022-3872 is a high-severity vulnerability in Qemu Qemu, published on 7 Nov 2022. 

### Official description

An off-by-one read/write issue was found in the SDHCI device of QEMU. It occurs when reading/writing the Buffer Data Port Register in sdhci_read_dataport and sdhci_write_dataport, respectively, if data_count == block_size. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.

Weakness: CWE-193 (Off-by-one Error)

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

It affects 1 product.


Products: Qemu Qemu.

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

Upgrade to a fixed version.

## Is CVE-2022-3872 being exploited?

There is no known exploitation of CVE-2022-3872 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-2022-3872 and fix it if it is affected.

What it is: CVE-2022-3872 is a high-severity vulnerability in Qemu Qemu, published on 7 Nov 2022. 
Exploitation: There is no known exploitation of CVE-2022-3872 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-2022-3872/ (Markdown: https://insights.sbomify.com/CVE-2022-3872/index.md)
```

## Sources

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

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