{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-99686","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-25T10:25:14.429Z","datePublished":"2026-11-20T05:50:31.888Z","dateUpdated":"2026-11-22T11:09:44.198Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-11-22T11:09:44.198Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nvhost: fix used ring index wrap in vhost_add_used_n_in_order\n\nvhost_add_used_n_in_order() advances start by nheads[i] but wraps it\nwith a single subtraction.  If start + nheads[i] >= 2 * vq->num, start\ncan remain outside the ring.\n\nWith used-ring logging enabled, start > vq->num makes (vq->num - start)\nunderflow.  log_write() then sets bits beyond the dirty-log bitmap,\npotentially corrupting adjacent userspace memory.  This is reachable on\nthe vhost-net TX path with VIRTIO_F_IN_ORDER: done_idx can reach\nVHOST_NET_BATCH (64), triggering the issue with a 32-entry ring.\n\nWrap start with a mask to keep it within the ring.  VHOST_SET_VRING_NUM\nenforces a nonzero power-of-two ring size, allowing start to be wrapped\nusing & (vq->num - 1)."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - Guest TX descriptors reach vhost_add_used_n_in_order through handle_tx_kick, handle_tx_copy, and vhost_tx_batch, which stores done_idx in vq->nheads[0] and calls vhost_net_signal_used with count 1. That batch count is what wraps start; a remote peer never supplies nheads or the used-ring index.\nAC:H - The guest can accept VIRTIO_F_IN_ORDER, select a 32-entry queue that QEMU programs with VHOST_SET_VRING_NUM, and kick a 64-buffer TX batch so one subtraction leaves start above vq->num. log_write runs only if vq->log_used is set, and only host userspace sets VHOST_VRING_F_LOG on VHOST_SET_VRING_ADDR; the guest cannot.\nPR:L - The guest does not pass vhost_dev_check_owner or open /dev/vhost-net. QEMU owns the device and issues the ioctls; the guest only publishes the TX avail ring and kicks it. That is control of a tenant VM's virtio-net queue, not host root in the init namespace.\nUI:N - The guest posts the TX buffers and fires the kick eventfd that wakes handle_tx_kick. No host user has to mount media or open an attacker-supplied file; used-ring logging is host state, not a victim action on attacker data.\nS:C - vhost_put_used writes one in-range used element before start advances, so the guest used ring is not the overflow. With vq->log_used, log_used feeds the underflow length to log_write and set_bit_to_user, which sets bits past the host dirty-log bitmap in the QEMU process.\nC:H - For num=32 and start left at 35, (vq->num - start) is an unsigned underflow and log_write is called with length 34359738344. set_bit_to_user then walks vq->log_base past the bitmap, a VMM heap smash that can disclose host memory held by QEMU rather than a few used-ring bytes.\nI:H - The same log_write loop is an out-of-bounds write: set_bit_to_user sets every bit from the used-ring log page onward until pin_user_pages_fast fails, turning adjacent QEMU heap bytes into 0xFF. That is host-process corruption, not an in-bounds used-ring update.\nA:H - The multi-gigabyte log_write loop runs inside the vhost worker on the TX kick path and ignores log_used's error, so it both stalls the virtqueue and smashes the QEMU address space that owns the vhost mm until the VMM crashes and the VM is gone."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/vhost/vhost.c"],"versions":[{"version":"67a873df0c410915275f735fedb401b9637d6faf","lessThan":"ebdc350cfb1740b6411420482e58a35cc4761628","status":"affected","versionType":"git"},{"version":"67a873df0c410915275f735fedb401b9637d6faf","lessThan":"308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0","status":"affected","versionType":"git"},{"version":"67a873df0c410915275f735fedb401b9637d6faf","lessThan":"e244725e86be02cd85cb878b3ed8570eba2e4be1","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/vhost/vhost.c"],"versions":[{"version":"6.17","status":"affected"},{"version":"0","lessThan":"6.17","status":"unaffected","versionType":"semver"},{"version":"6.18.64","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.3.5","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.17","versionEndExcluding":"6.18.64"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.17","versionEndExcluding":"7.3.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.17","versionEndExcluding":"7.4-rc2"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/ebdc350cfb1740b6411420482e58a35cc4761628"},{"url":"https://git.kernel.org/stable/c/308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0"},{"url":"https://git.kernel.org/stable/c/e244725e86be02cd85cb878b3ed8570eba2e4be1"}],"title":"vhost: fix used ring index wrap in vhost_add_used_n_in_order","x_generator":{"engine":"bippy-1.2.0"}}}}