# CVE-2024-51565: bhyve(8) hda driver buffer over-read

> A buffer over-read in the FreeBSD bhyve hda driver allows guest-controlled values to cause memory corruption, potentially leading to denial of service or information disclosure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-hx7r-qwxv-w9j9

## What is CVE-2024-51565?

CVE-2024-51565 is a medium-severity memory corruption vulnerability in FreeBSD, published on 12 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The hda driver is vulnerable to a buffer over-read from a guest-controlled value.

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

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


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

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

## Is CVE-2024-51565 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51565 is a medium-severity memory corruption vulnerability in FreeBSD, published on 12 Nov 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-51565 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-51565/ (Markdown: https://insights.sbomify.com/CVE-2024-51565/index.md)
```

## Sources

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

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