# CVE-2024-41721: bhyve(8) out-of-bounds read access via XHCI emulation

> An out-of-bounds read in FreeBSD's bhyve XHCI emulation can lead to arbitrary write and remote code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2024
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-77f2-r3qh-x5x7

## What is CVE-2024-41721?

CVE-2024-41721 is a high-severity memory corruption vulnerability in FreeBSD, published on 20 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An insufficient boundary validation in the USB code could lead to an out-of-bounds read on the heap, which could potentially lead to an arbitrary write and remote code execution.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

No fix has been published for CVE-2024-41721 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-41721 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41721 is a high-severity memory corruption vulnerability in FreeBSD, published on 20 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41721 in the wild and no public exploit code.

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

## Sources

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

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