CVE-2026-74356

published 15 Aug 2026 · updated 15 Nov 2026

vhost: fix vhost_get_avail_idx for a non empty ring

7.4HighCVSS 7.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e115471008111f894c6528d9ab2ce7d0ce306f35, Kernel 09861858a68342f851f71c669ac0f69865c32151, Kernel 0fe5ca2d56f0122988016e415a074c95925504b7 and 8 more.

In the Linux kernel, the following vulnerability has been resolved: vhost: fix vhost_get_avail_idx for a non empty ring vhost_get_avail_idx is supposed to report whether it has updated vq->avail_idx. Instead, it returns whether all entries have been consumed, which is usually the same. But not always - in drivers/vhost/net.c and when mergeable buffers have been enabled, the driver checks whether the combined entries are big enough to store an incoming packet. If not, the driver re-enables notifications with available entries still in the ring. The incorrect return value from vhost_get_avail_idx propagates through vhost_enable_notify and causes the host to livelock if the guest is not making progress, as vhost will immediately disable notifications and retry using the available entries. This goes back to commit d3bb267bbdcb ("vhost: cache avail index in vhost_enable_notify()") which changed vhost_enable_notify() to compare the freshly read avail index against vq->last_avail_idx instead of the previously cached vq->avail_idx. Commit 7ad472397667 ("vhost: move smp_rmb() into vhost_get_avail_idx()") then carried over the same comparison when refactoring vhost_enable_notify() to call the unified vhost_get_avail_idx(). The obvious fix is to make vhost_get_avail_idx do what the comment says it does and report whether new entries have been added.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=d3bb267bbdcba199568f1325743d9d501dea0560 <e115471008111f894c6528d9ab2ce7d0ce306f35, >=d3bb267bbdcba199568f1325743d9d501dea0560 <09861858a68342f851f71c669ac0f69865c32151, >=d3bb267bbdcba199568f1325743d9d501dea0560 <0fe5ca2d56f0122988016e415a074c95925504b7, >=d3bb267bbdcba199568f1325743d9d501dea0560 <7536f8f72bd24f1ae316c24231faaa3667eba837, >=d3bb267bbdcba199568f1325743d9d501dea0560 <7f229d27bf27c7e589eca690d8612763a7a4801f, >=d3bb267bbdcba199568f1325743d9d501dea0560 <a9326b652bc7acd748d7a1143573845c7924d847, =5.18e115471008111f894c6528d9ab2ce7d0ce306f35, 09861858a68342f851f71c669ac0f69865c32151, 0fe5ca2d56f0122988016e415a074c95925504b7, 7536f8f72bd24f1ae316c24231faaa3667eba837, 7f229d27bf27c7e589eca690d8612763a7a4801f, a9326b652bc7acd748d7a1143573845c7924d847
linux-kernel: Kernel>=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.160, >=6.7.0 <6.12.97, >=5.18.0 <6.1.1916.18.40, 7.1.5, 6.6.160, 6.12.97, 6.1.191

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-74356 severity on Zeptric[![CVE-2026-74356](https://zeptric.io/badge/cve/CVE-2026-74356.svg)](https://zeptric.io/cve/CVE-2026-74356)