CVE-2026-74356vhost: fix vhost_get_avail_idx for a non empty ring
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.4 HIGH (v3.1, CNA)CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from d3bb267bbdcba199568f1325743d9d501dea0560 before e115471008111f894c6528d9ab2ce7d0ce306f35; from d3bb267bbdcba199568f1325743d9d501dea0560 before 7f229d27bf27c7e589eca690d8612763a7a4801f; from d3bb267bbdcba199568f1325743d9d501dea0560 before a9326b652bc7acd748d7a1143573845c7924d847; from d3bb267bbdcba199568f1325743d9d501dea0560 before 09861858a68342f851f71c669ac0f69865c32151 | CNA record |
References
- https://git.kernel.org/stable/c/e115471008111f894c6528d9ab2ce7d0ce306f35
- https://git.kernel.org/stable/c/7f229d27bf27c7e589eca690d8612763a7a4801f
- https://git.kernel.org/stable/c/a9326b652bc7acd748d7a1143573845c7924d847
- https://git.kernel.org/stable/c/09861858a68342f851f71c669ac0f69865c32151
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.