Skip to content
Threat Brief

← All advisories

CVE-2026-97994

Medium 5.5No known exploitationFix available

vhost/vdpa: reject VRING_NUM larger than device max

Record last updated

CVSS score

5.5

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 11% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: vhost/vdpa: reject VRING_NUM larger than device max vhost_vring_set_num() accepts any non-zero power-of-two queue size that fits in 16 bits. vhost-vdpa then passes that value to set_vq_num() without comparing it with get_vq_num_max(). A process with access to /dev/vhost-vdpa-* can therefore configure a queue larger than the device advertises. With vdpa_sim, the worker can walk descriptors beyond the mapped descriptor ring. KASAN reports a 16-byte out-of-bounds read, corresponding to one vring_desc, in the vringh IOTLB path: BUG: KASAN: out-of-bounds in _copy_from_iter Read of size 16 copy_from_iotlb copydesc_iotlb vringh_getdesc_iotlb vdpasim_net_work Cache get_vq_num_max() immediately after reset. Some backends derive it from writable queue-size state, so querying it after SET_NUM may return the current size instead of the device capability. Invalidate the cached value before reset so a failed reset leaves SET_NUM disabled. For VHOST_SET_VRING_NUM, copy the complete vring state once and use the same index and size for validation, vq->num, and set_vq_num(). This ensures that validation and use operate on the same copied values.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 4c8cf31885f69e86be0b5b9e6677a26797365e1d before ccb1dc7c527f8c925925cf92afc76ae590dac311ccb1dc7c527f8c925925cf92afc76ae590dac311CVE Program
LinuxLinuxfrom 4c8cf31885f69e86be0b5b9e6677a26797365e1d before 4875c65ca53797a0a402fe2bb54d1b12f28b3cda4875c65ca53797a0a402fe2bb54d1b12f28b3cdaCVE Program
LinuxLinuxfrom 4c8cf31885f69e86be0b5b9e6677a26797365e1d before 1d09201d81b7d3e276860cc7b7dbf6c6cbe8e9b41d09201d81b7d3e276860cc7b7dbf6c6cbe8e9b4CVE Program
LinuxLinuxfrom 4c8cf31885f69e86be0b5b9e6677a26797365e1d before 68232102f20fc961327fb9e0f605a7eaadf030a968232102f20fc961327fb9e0f605a7eaadf030a9CVE Program
LinuxLinuxfrom 4c8cf31885f69e86be0b5b9e6677a26797365e1d before 59522639a7d71cff4e20d594d0b9ea30dd0c77e059522639a7d71cff4e20d594d0b9ea30dd0c77e0CVE Program
LinuxLinux5.7Not documentedCVE Program
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documented6.6.158.1-1Microsoft MSRC
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.12.111 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.53 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.6.158 up to and including 6.6.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.7 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 5.7Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references