Reachable assertion in illumos bhyve REP string instruction emulation allows guest to panic host
illumos-gate · OmniOS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| illumos illumos-gate x86 |
| No fix yet |
| OmniOS OmniOS |
| No fix yet |
illumos-gate · OmniOS
| Product | Affected | Fixed in |
|---|---|---|
| illumos illumos-gate x86 |
| No fix yet |
| OmniOS OmniOS |
| No fix yet |
A reachable assertion in the illumos bhyve instruction emulator allows a guest to panic the host. When emulating a REP-prefixed MOVS or STOS instruction that accesses guest MMIO, vie_emulate_movs() and vie_emulate_stos() in usr/src/uts/intel/io/vmm/vmm_instruction_emul.c do not clear the VIES_REPEAT status flag on the final iteration. For MMIO regions emulated in the kernel (the local APIC, I/O APIC and HPET), the stale flag causes a VERIFY assertion in vie_advance_pc() to fail, and the host panics. A privileged user within a guest VM can issue a REP MOVS or REP STOS instruction against the local APIC page to cause a denial of service of the host and every other guest running on it. The flaw has existed since 2020 (illumos-gate commit e0c0d44e), and affects any illumos distribution prior to illumos-gate commit 696ecf8d.
From the CVE record · illumos
A reachable assertion in the illumos bhyve instruction emulator can panic the host. A privileged user inside a guest VM can trigger it with a REP-prefixed MOVS or STOS instruction targeting kernel-emulated guest MMIO, disrupting the host and other guests. No host-side authentication or user interaction is described.
Operators of illumos distributions, including OmniOS, running bhyve should check systems with illumos-gate code prior to commit 696ecf8d.