FreeBSD bhyve hypervisor flaws fixed
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
Five vulnerabilities in FreeBSD's bhyve hypervisor let a malicious guest VM crash the host or execute code in host userspace; patches available.
NCSC-NL published an advisory covering five vulnerabilities in the FreeBSD bhyve hypervisor, affecting device emulation models including USB 3, HDA audio, and framebuffer. The flaws stem from race conditions, improper validation, and synchronization issues: manipulation of event ring size and Transfer Request Block (TRB) fields in the USB 3 device model, out-of-bounds memory access via improperly checked zero-length Buffer Descriptor List entries in the HDA audio device model, and duplicate/unsynchronized constants plus missing resolution-parameter validation in the framebuffer device model.
A malicious guest virtual machine can exploit these issues to cause denial of service by crashing the bhyve process, or to achieve arbitrary code execution in the host userspace — a serious concern for multi-tenant virtualization environments where guest isolation is a core security boundary. The vulnerabilities are specific to systems running the bhyve hypervisor. FreeBSD has released updates addressing all five CVEs (CVE-2026-101307 through CVE-2026-101311), with CVSS scores ranging from 5.5 to 8.2. No in-the-wild exploitation is reported; this is a vendor-patched disclosure.
Defenders running FreeBSD bhyve should apply the available updates promptly, particularly in environments hosting untrusted or multi-tenant guest VMs, given the potential for guest-to-host escape via code execution.
Mentioned in this report
Source reporting: https://advisories.ncsc.nl/2026/ncsc-2026-0452.html
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 13,932 reports from 143 sources, 508 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs