CVE-2026-74356
CVE CVE-2026-74356EUVD EUVD-2026-59503Published 2026-08-15T05:58:41.000ZLast changed 2026-08-17T05:46:17.000ZCVSS 7.4
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 0; 5.18; patch: 7.1.5; patch: 6.18.40; d3bb267bbdcba199568f1325743d9d501dea0560 <09861858a68342f851f71c669ac0f69865c32151; patch: 6.12.97; d3bb267bbdcba199568f1325743d9d501dea0560 <a9326b652bc7acd748d7a1143573845c7924d847; d3bb267bbdcba199568f1325743d9d501dea0560 <e115471008111f894c6528d9ab2ce7d0ce306f35; patch: 7.2; d3bb267bbdcba199568f1325743d9d501dea0560 <7f229d27bf27c7e589eca690d8612763a7a4801f
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.