Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99686

vhost: fix used ring index wrap in vhost_add_used_n_in_order

No exploitation reported by the sources we read.

  • Published2026-11-20
  • Fixed in7.3.5 · 6.18.64

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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

Timeline

dates in UTC
  1. 2026-11-2005:50CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.57.3.5
6.x≥ 6.17.0, < 6.18.646.18.64

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 67a873df0c410915275f735fedb401b9637d6faf, < ebdc350cfb1740b6411420482e58a35cc4761628fixed in ebdc350cfb1740b6411420482e58a35cc4761628git
    • ≥ 67a873df0c410915275f735fedb401b9637d6faf, < 308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0fixed in 308e148cf771ed36ad8cd7ef0e9bee2f7ec478d0git
    • ≥ 67a873df0c410915275f735fedb401b9637d6faf, < e244725e86be02cd85cb878b3ed8570eba2e4be1fixed in e244725e86be02cd85cb878b3ed8570eba2e4be1git
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 6.17no fix stated

    Not affected < 6.17 · ≥ 6.18.64, ≤ 6.18.* · ≥ 7.3.5, ≤ 7.3.* · ≥ 7.4-rc2

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-20

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • linuxDebian:14all versions · no fixed version listed
  • linux-ltsAlpaquita:streamfrom 6.18.62-r0 · fixed in 6.18.64-r0

Vendor advisories

  • CVE-2026-99686 Red Hat Product Security14 known affected

    kernel: kernel: vhost: memory corruption via improper ring index calculation

    kernel as a component of Red Hat Enterprise Linux 6 · kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6 · kernel-bootwrapper as a component of Red Hat Enterprise Linux 6 · +11 more

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.5 · 6.18.64
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-99686 · 14 productsAffected

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Published
2026-11-20
Last modified
2026-11-22
NVD status
Received
GitHub advisory
GHSA-w95v-vg5c-p3hj

Frequently asked questions

What is CVE-2026-99686?

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

Is CVE-2026-99686 actively exploited?

Active exploitation of CVE-2026-99686 has not been confirmed. Its EPSS score was 0.2% on 2026-11-21, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99686?

CVE-2026-99686 has a CVSS v3 base score of 7.8 (High severity), with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website checks · 250 API requests/month

Sources for this record