CVE-2022-23087 is a high severity out-of-bounds write in the emulated e1000 network adapter of the FreeBSD bhyve hypervisor, scored 8.8 by NVD. A misbehaving guest could overwrite host process memory. Update FreeBSD and restart guests, or give guests virtio-net instead of e1000.
What's affected
FreeBSD advisory SA-22:05 says all supported versions at the time were affected: 13.0, 13.1 at release candidate stage, and 12.3. Only the e1000 device model is affected, and the virtio-net device is not.
Corrections were committed on 2022-04-05 for stable/13 and stable/12, and on 2022-04-06 for the release branches. Fixed release levels are 13.1-RC1-p1, 13.0-RELEASE-p11 and 12.3-RELEASE-p5. After updating, restart the affected bhyve virtual machines or reboot the host.
The impact line in the advisory is that a misbehaving guest could overwrite memory in the bhyve process on the host, possibly leading to code execution in the host context. The bhyve process runs in a Capsicum sandbox, which, depending on the FreeBSD version and bhyve configuration, limits what exploitation can achieve.
NVD scores the flaw 8.8 with a changed scope. The advisory carries no numeric score of its own.
Weakness class per the record: CWE-787.
How to check if you're exposed
Find bhyve guests that use the e1000 emulation. In the VM configuration, look for the network device type:
grep -rE 'e1000' /vm /etc 2>/dev/null
ps ax | grep '[b]hyve'
A bhyve command line with e1000 as the network device type means the vulnerable model is in use. A guest using virtio-net is not affected by this issue.
Next, check the host patch level with freebsd-version -ku and compare it with the fixed levels above. Note that guests keep running with the old process until they are restarted, so patching the host without restarting guests leaves them on the old code.
What to do now
- List bhyve guests and which network device model each uses.
- Switch guests to virtio-net where the guest operating system supports it, since the advisory names this as a workaround.
- Update the host with freebsd-update or the signed source patch.
- Restart every bhyve guest, or reboot the host, so the patched bhyve is the one running.
Why it matters
The e1000 model builds a modified packet header in an on-stack buffer when the guest asks for checksum offload. The guest supplied the checksum offset, and the code did not validate that offset for certain packet types. A guest that sets a bad offset can write outside the buffer in the bhyve process, which is an out-of-bounds write.
This is a hypervisor escape class of bug: the guest is meant to be untrusted, and the device emulation code is the boundary. Emulated hardware is a well known place for flaws because it parses attacker influenced data written by the guest.
The Capsicum sandbox is a real mitigation, but it is not a reason to delay. Using virtio-net removes the vulnerable model entirely for guests that can run it.
Quick check
Is the virtio-net device affected?
No. The advisory states that only the e1000 device model is affected and that presenting only virtio-net to the guest is a suitable workaround if the guest supports it.
Sources
Last reviewed: 19 October 2026.