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.
Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 15 Oct 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The xHCI (USB 3) device model did not validate or save the event ring size provided by the guest. The size was re-read from guest memory on each use, and Transfer Request Block (TRB) fields were loaded without protection against concurrent modification by the guest. This race condition could be triggered by a guest running malicious, privileged code. 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. | |
| Title | Multiple vulnerabilities in bhyve device models | |
| Weaknesses | CWE-362 | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: freebsd
Published:
Updated: 2026-10-15T15:47:58.877Z
Reserved: 2026-09-28T13:33:02.324Z
Link: CVE-2026-101309
No data.
Status : Received
Published: 2026-10-15T08:16:36.197
Modified: 2026-10-15T08:16:36.197
Link: CVE-2026-101309
No data.
OpenCVE Enrichment
No data.
-
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')