FreeBSD bhyve EUVD-2026-101931

Exploitation requires the attacker to be operating a bhyve virtual machine as a privileged guest, with the ability to interact with the emulated Intel HDA audio device - specifically to configure its Buffer Descriptor List and start an audio stream. The concrete trigger is a BDL containing a zero-length entry combined with guest modification of BDL fields AFTER the hypervisor's validation step (a TOCTOU window) during DMA transfer processing. Limiting factors that reduce realistic risk: access is local to the host via a controlled guest (AV:L), guest privileges are required (PR:L - the attacker must already control device programming, i.e. guest kernel/driver level), no user interaction is involved, exploitation complexity is high due to the required post-validation race, and any resulting host-side code execution is confined by bhyve's Capsicum sandbox. Hosts not exposing the HDA audio device to untrusted guests are not affected.

This is a genuine but conditional priority rather than a drop-everything emergency. The input CVSS vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H = 7.0) correctly captures a local, high-complexity, privilege-requiring flaw: the attacker must already be executing privileged code inside a bhyve guest to program the emulated HDA device's Buffer Descriptor List. The high attack complexity (AC:H) is well justified by the description's TOCTOU element - 'BDL fields were also subject to modification by the guest after validation' - meaning reliable exploitation depends on winning a race, which suppresses real-world exploitability. All exploitation signals point the same way: EPSS is only 0.18% (7th percentile), there is no CISA KEV listing, and no public exploit code was identified, so there is no evidence of active or imminent mass exploitation. The one point of tension worth flagging is CVSS scope: the vendor vector sets S:U, but this is a guest-to-host hypervisor boundary crossing (code execution in host userspace from inside a VM), which under CVSS 3.1 conventions usually warrants S:C - see assessed vector below. A mitigating control is explicitly noted by the vendor: bhyve runs inside a Capsicum sandbox, which constrains what host-code execution can reach. Net: real and patch-worthy for anyone running bhyve with emulated HDA audio, but low urgency given local+privileged+high-complexity access and no exploitation activity.

An attacker who has already gained privileged (kernel/driver-level) code execution inside a bhyve guest programs the emulated HDA audio controller with a Buffer Descriptor List containing a zero-length entry, then mutates BDL fields after the hypervisor validates them. When the stream starts and DMA processing runs, the host-side bhyve process performs an out-of-bounds read or write, crashing the VM process or potentially achieving arbitrary code execution in the host userspace context (constrained by Capsicum). No public exploit code was identified at time of analysis, and the required race makes reliable exploitation difficult.