PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-74356 Linux CVE debrief

The Linux kernel has a vulnerability in the vhost component, specifically in the `vhost_get_avail_idx` function. This function is supposed to report whether it has updated `vq->avail_idx`, but it incorrectly returns whether all entries have been consumed. This can cause the host to livelock if the guest is not making progress, as vhost will immediately disable notifications and retry using the available entries.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-15
Original CVE updated
2026-10-21
Advisory published
2026-08-15
Advisory updated
2026-10-21

Who should care

Defenders responsible for Linux kernel-based systems, particularly those using the vhost component, should assess exposure and prioritize patching. System administrators and security teams should verify kernel versions and apply patches to prevent potential livelock issues.

Why it matters

The Linux kernel vulnerability in the vhost component can cause a livelock in the host, and defenders should prioritize verifying kernel versions and applying patches to prevent potential issues.

  • Potential livelock in the host due to incorrect return value from `vhost_get_avail_idx`
  • Need to verify Linux kernel version and apply patches to fix the vulnerability
  • Potential impact on system performance and stability

Technical summary

The `vhost_get_avail_idx` function in the Linux kernel incorrectly returns whether all entries have been consumed, instead of reporting whether it has updated `vq->avail_idx`. This can cause the host to livelock if the guest is not making progress. The issue was introduced by commit d3bb267bbdcb and was fixed by multiple subsequent commits. Defenders should prioritize verifying the Linux kernel version and applying patches to fix the vulnerability. They should also monitor for potential livelock issues in the vhost component and review system configurations to ensure that vhost is properly configured.

Defensive priority

Defenders should prioritize verifying the Linux kernel version and applying patches to fix the vulnerability. They should also monitor for potential livelock issues in the vhost component.

Recommended defensive actions

  • Verify Linux kernel version and apply patches to fix the vulnerability
  • Monitor for potential livelock issues in the vhost component
  • Review system configurations and ensure that vhost is properly configured
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The vulnerability is caused by an incorrect return value from `vhost_get_avail_idx`, which can lead to a livelock in the host. The issue was introduced by commit d3bb267bbdcb and was fixed by multiple subsequent commits.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-74356 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-74356

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-74356 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-74356

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • vhost: fix vhost_get_avail_idx for a non empty ring

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/74xxx/CVE-2026-74356.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/0fe5ca2d56f0122988016e415a074c95925504b7

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/e115471008111f894c6528d9ab2ce7d0ce306f35

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/7f229d27bf27c7e589eca690d8612763a7a4801f

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a9326b652bc7acd748d7a1143573845c7924d847

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/09861858a68342f851f71c669ac0f69865c32151

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.