Bug 2577675 (CVE-2026-99686) - CVE-2026-99686 kernel: kernel: vhost: memory corruption via improper ring index calculation
Summary: CVE-2026-99686 kernel: kernel: vhost: memory corruption via improper ring ind...
Keywords:
Status: NEW
Alias: CVE-2026-99686
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 06:07 UTC by OSIDB Bzimport
Modified: 2026-11-20 10:14 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 06:07:41 UTC
In the Linux kernel, the following vulnerability has been resolved:

vhost: fix used ring index wrap in vhost_add_used_n_in_order

vhost_add_used_n_in_order() advances start by nheads[i] but wraps it
with a single subtraction.  If start + nheads[i] >= 2 * vq->num, start
can remain outside the ring.

With used-ring logging enabled, start > vq->num makes (vq->num - start)
underflow.  log_write() then sets bits beyond the dirty-log bitmap,
potentially corrupting adjacent userspace memory.  This is reachable on
the vhost-net TX path with VIRTIO_F_IN_ORDER: done_idx can reach
VHOST_NET_BATCH (64), triggering the issue with a 32-entry ring.

Wrap start with a mask to keep it within the ring.  VHOST_SET_VRING_NUM
enforces a nonzero power-of-two ring size, allowing start to be wrapped
using & (vq->num - 1).


Note You need to log in before you can comment on or make changes to this bug.