# CVE-2026-101310: Multiple vulnerabilities in bhyve device models

> A malicious guest can trigger out-of-bounds memory access in the bhyve HDA audio device model, potentially leading to host code execution or denial of service.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/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:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-gf8p-jhgw-8hg8

## What is CVE-2026-101310?

CVE-2026-101310 is a high-severity memory corruption vulnerability in FreeBSD, published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The HDA audio device model did not check for zero-length Buffer Descriptor List (BDL) entries when starting a stream.  A zero-length entry caused an out-of-bounds read or write during DMA transfer processing.  BDL fields were also subject to modification by the guest after validation.

A malicious guest can crash the bhyve process or potentially execute arbitrary code in the host userspace context running the virtual machine, subject to bhyve's Capsicum sandbox.

Weakness: CWE-787 (Out-of-bounds Write), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), CWE-126 (Buffer Over-read)

## Which versions are affected by CVE-2026-101310?


## How do I fix CVE-2026-101310?

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

## Is CVE-2026-101310 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101310 and fix it if it is affected.

What it is: CVE-2026-101310 is a high-severity memory corruption vulnerability in FreeBSD, published on 15 Oct 2026. 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-2026-101310 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-2026-101310/ (Markdown: https://insights.sbomify.com/CVE-2026-101310/index.md)
```

## Sources

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

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