Skip to main content
VulnerabilityPublished

CVE-2026-99686: Linux kernel · vhost: fix used ring index wrap in vhost_add_used_n_in_order

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99686· High

Not known to be exploited · fixed in ebdc350cfb1740b6411420482e58a35cc4761628 : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in ebdc350cfb1740b6411420482e58a35cc4761628, e244725e86be02cd85cb878b3ed8570eba2e4be1, 308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to ebdc350cfb1740b6411420482e58a35cc4761628, e244725e86be02cd85cb878b3ed8570eba2e4be1 or 308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 67a873df0c410915275f735fedb401b9637d6faf, < ebdc350cfb1740b6411420482e58a35cc4761628
Fixed in
  • ebdc350cfb1740b6411420482e58a35cc4761628
LinuxLinuxAffected
  • ≥ 67a873df0c410915275f735fedb401b9637d6faf, < e244725e86be02cd85cb878b3ed8570eba2e4be1
Fixed in
  • e244725e86be02cd85cb878b3ed8570eba2e4be1
LinuxLinuxAffected
  • ≥ 67a873df0c410915275f735fedb401b9637d6faf, < 308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0
Fixed in
  • 308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0
LinuxLinuxAffected
  • =6.17
Fixed in–

Description

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).

References

Community reviews

Loading reviews…