{"cve":"CVE-2026-97994","nvd":{"published":"2026-09-25T11:17:27.637","modified":"2026-10-19T10:17:50.850","status":"Received","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvhost/vdpa: reject VRING_NUM larger than device max\n\nvhost_vring_set_num() accepts any non-zero power-of-two queue size that\nfits in 16 bits. vhost-vdpa then passes that value to set_vq_num()\nwithout comparing it with get_vq_num_max().\n\nA process with access to /dev/vhost-vdpa-* can therefore configure a\nqueue larger than the device advertises. With vdpa_sim, the worker can\nwalk descriptors beyond the mapped descriptor ring. KASAN reports a\n16-byte out-of-bounds read, corresponding to one vring_desc, in the\nvringh IOTLB path:\n\n  BUG: KASAN: out-of-bounds in _copy_from_iter\n  Read of size 16\n  copy_from_iotlb\n  copydesc_iotlb\n  vringh_getdesc_iotlb\n  vdpasim_net_work\n\nCache get_vq_num_max() immediately after reset. Some backends derive\nit from writable queue-size state, so querying it after SET_NUM may\nreturn the current size instead of the device capability. Invalidate\nthe cached value before reset so a failed reset leaves SET_NUM\ndisabled.\n\nFor VHOST_SET_VRING_NUM, copy the complete vring state once and use\nthe same index and size for validation, vq->num, and set_vq_num().\nThis ensures that validation and use operate on the same copied values.","cvss_v4":null,"cvss_v3":null,"cwes":[],"references":["https://git.kernel.org/stable/c/1d09201d81b7d3e276860cc7b7dbf6c6cbe8e9b4","https://git.kernel.org/stable/c/4875c65ca53797a0a402fe2bb54d1b12f28b3cda","https://git.kernel.org/stable/c/59522639a7d71cff4e20d594d0b9ea30dd0c77e0","https://git.kernel.org/stable/c/68232102f20fc961327fb9e0f605a7eaadf030a9","https://git.kernel.org/stable/c/ccb1dc7c527f8c925925cf92afc76ae590dac311"],"products":[],"source":"nvd","synced_at":"2026-10-19T22:56:02.509636177+00:00"},"epss":{"cve":"CVE-2026-97994","score":0.00206,"percentile":0.10464,"date":"2026-10-25"},"kev":null,"osv":[],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}