CVE-2026-97994: Linux kernel · vhost/vdpa: reject VRING_NUM larger than device max
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ccb1dc7c527f8c925925cf92afc76ae590dac311 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ccb1dc7c527f8c925925cf92afc76ae590dac311, 68232102f20fc961327fb9e0f605a7eaadf030a9, 59522639a7d71cff4e20d594d0b9ea30dd0c77e0 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
This vulnerability has been fixed in the Linux kernel. Users should update to a fixed kernel version containing the commits identified (e.g., ccb1dc7c527f8c925925cf92afc76ae590dac311 and others). No additional mitigation is required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's vhost/vdpa subsystem allowed processes with access to /dev/vhost-vdpa-* to configure a queue size larger than the device's maximum. This could lead to out-of-bounds reads in the descriptor ring, as detected by KASAN. The issue was addressed by validating and caching the maximum queue size properly and ensuring consistent use of vring state during configuration.
References
- git.kernel.org/stable/c/4875c65ca53797a0a402fe2bb54d1b12f28b3cda (opens in a new tab)
- git.kernel.org/stable/c/1d09201d81b7d3e276860cc7b7dbf6c6cbe8e9b4 (opens in a new tab)
- git.kernel.org/stable/c/68232102f20fc961327fb9e0f605a7eaadf030a9 (opens in a new tab)
- git.kernel.org/stable/c/59522639a7d71cff4e20d594d0b9ea30dd0c77e0 (opens in a new tab)
- git.kernel.org/stable/c/ccb1dc7c527f8c925925cf92afc76ae590dac311 (opens in a new tab)