# CVE-2010-0297: Memory corruption in n/a

> Guest OS users can trigger a buffer overflow in QEMU's USB handling to crash the guest or execute arbitrary code on the host.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 12 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r7ff-53hm-m6vh

## What is CVE-2010-0297?

CVE-2010-0297 is a high-severity memory corruption vulnerability in Qemu Qemu, published on 12 Feb 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in the usb_host_handle_control function in the USB passthrough handling implementation in usb-linux.c in QEMU before 0.11.1 allows guest OS users to cause a denial of service (guest OS crash or hang) or possibly execute arbitrary code on the host OS via a crafted USB packet.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2010-0297?

It affects 1 product.


Products: Qemu Qemu.

## How do I fix CVE-2010-0297?

Upgrade to a fixed version.

## Is CVE-2010-0297 being exploited?

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

What it is: CVE-2010-0297 is a high-severity memory corruption vulnerability in Qemu Qemu, published on 12 Feb 2010. 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-2010-0297 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-2010-0297/ (Markdown: https://insights.sbomify.com/CVE-2010-0297/index.md)
```

## Sources

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

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