Skip to main content
Vulnerability Database/CVE-2026-101309

CVE-2026-101309: bhyve xHCI Race Condition Vulnerability

CVE-2026-101309 is a race condition vulnerability in bhyve's xHCI USB 3 device model that allows malicious guests to crash the hypervisor or execute code. This article covers the technical details, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-101309 Overview

CVE-2026-101309 is a race condition in the FreeBSD bhyve hypervisor's xHCI (USB 3) device model. The device model does not validate or persist the event ring size supplied by the guest. Instead, it re-reads the size and Transfer Request Block (TRB) fields from guest memory on each use, without protection against concurrent modification. A guest running malicious, privileged code can exploit the resulting time-of-check to time-of-use (TOCTOU) window [CWE-362] to crash the bhyve process or execute arbitrary code in the host userspace context. The impact is bounded by the Capsicum sandbox applied to bhyve.

Critical Impact

A malicious privileged guest can escape the virtual machine boundary and execute arbitrary code in the host userspace running bhyve, constrained only by Capsicum.

Affected Products

  • FreeBSD operating system
  • FreeBSD bhyve hypervisor
  • bhyve xHCI (USB 3) emulated device model

Discovery Timeline

  • 2026-10-15 - CVE-2026-101309 published to the National Vulnerability Database
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-101309

Vulnerability Analysis

The bhyve xHCI device model emulates a USB 3 host controller for guest virtual machines. The controller uses an event ring, a circular buffer in guest memory, to deliver completion events to the guest. Each entry in the ring is a Transfer Request Block (TRB).

The emulation layer reads both the event ring size and TRB field contents directly from guest memory each time it processes an event. Because a privileged guest can modify this memory concurrently from another vCPU, the values observed during validation can differ from the values used in subsequent processing. This TOCTOU condition allows the guest to drive the host emulator into out-of-bounds memory access or state corruption.

Root Cause

The root cause is improper synchronization and missing validation state caching in the xHCI event ring handling path. The event ring size is a guest-controlled value that should be validated once and stored, but the implementation re-reads it on each access. TRB fields are likewise fetched without copying to a local buffer, leaving every field subject to concurrent mutation between the check and the use.

Attack Vector

Exploitation requires privileged code execution inside the guest VM. The attacker uses one vCPU to issue xHCI operations that cause the host to walk the event ring, while a second vCPU concurrently rewrites the ring size and TRB contents in shared guest memory. By racing the host emulator, the attacker steers it into inconsistent state. The outcome ranges from a bhyve process crash, resulting in guest denial of service, to arbitrary code execution in the bhyve userspace process on the host. Capsicum sandboxing limits what the attacker-controlled code can reach after escape.

Technical specifics are documented in the FreeBSD Security Advisory SA-26:72.

Detection Methods for CVE-2026-101309

Indicators of Compromise

  • Unexpected bhyve process crashes or segmentation faults in host system logs
  • Guest VMs with attached emulated USB 3 (xHCI) controllers terminating abnormally
  • Core dumps from bhyve referencing xHCI event ring or TRB handling functions
  • Host userspace processes spawned by or from bhyve performing unexpected activity within Capsicum constraints

Detection Strategies

  • Monitor FreeBSD host logs (/var/log/messages, dmesg) for repeated bhyve termination events tied to specific guests
  • Audit guest VM configurations to inventory which guests expose xHCI (USB 3) emulation
  • Correlate guest kernel activity with host-side bhyve instability to identify suspect tenants

Monitoring Recommendations

  • Enable process accounting on FreeBSD hypervisor hosts to track bhyve lifecycle events
  • Ship host audit logs to a centralized analytics platform for cross-host correlation of bhyve crashes
  • Alert on new or unexpected child processes under the bhyve process tree

How to Mitigate CVE-2026-101309

Immediate Actions Required

  • Apply the FreeBSD security update referenced in FreeBSD Security Advisory SA-26:72
  • Restart affected guest VMs after patching the host to ensure the fixed bhyve binary is in use
  • Inventory guests permitted to run privileged workloads and prioritize patching for multi-tenant hosts

Patch Information

FreeBSD has published fixes through the official security advisory process. Administrators should install the patched bhyve binary via freebsd-update or by rebuilding from the corresponding source branch, then restart guest VMs. Refer to the FreeBSD Security Advisory SA-26:72 for exact version and patch commit information.

Workarounds

  • Remove the emulated xHCI (USB 3) controller from guest configurations where USB 3 passthrough is not required
  • Restrict guest administrative access to trusted operators until the host is patched
  • Avoid running untrusted or multi-tenant workloads on unpatched bhyve hosts
bash
# Remove the xHCI (USB 3) device from a bhyve guest configuration
# Review the guest's device list and omit the '-s <slot>,xhci,...' argument
# Example: patch the host, then restart the guest without xHCI emulation
freebsd-update fetch
freebsd-update install
service vmd restart   # or restart individual bhyve guests as applicable

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.