PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-74310 Linux CVE debrief

A use-after-free vulnerability exists in the Linux kernel's vhost/net component. When a zerocopy TX descriptor is completed, the associated ubuf_info is not properly handled, leading to a potential crash or code execution. The vulnerability is caused by vhost_zerocopy_complete() treating every ubuf callback as a completed vhost descriptor, even when the callback only releases a cloned skb reference.

Vendor
Linux
Product
Unknown
CVSS
CRITICAL 9.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-15
Original CVE updated
2026-10-16
Advisory published
2026-08-15
Advisory updated
2026-10-16

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems, particularly those responsible for vulnerability management, system security, and patch management. They should assess exposure and apply patches or updates to mitigate the vulnerability. Additionally, security teams and operators of Linux-based systems should review the vulnerability and take necessary actions to protect their systems.

Why it matters

The CVE-2026-74310 vulnerability in the Linux kernel's vhost/net component can lead to system crashes or potential code execution. Linux kernel developers, maintainers, and users of Linux-based systems should assess exposure and apply patches or updates to mitigate the vulnerability.

  • Potential system crash or code execution
  • Elevation of privileges within the Linux kernel
  • Denial of service (DoS) via exploitation of the vulnerability

Technical summary

The vulnerability exists in the vhost/net component of the Linux kernel. The issue arises from the improper handling of ubuf_info in vhost_zerocopy_complete(). This function incorrectly assumes that every ubuf callback corresponds to a completed vhost descriptor, leading to potential use-after-free issues. The affected versions of the Linux kernel are identified, and the fix is included in specific commits. Linux kernel developers, maintainers, and users of Linux-based systems should assess exposure and apply patches or updates to mitigate the vulnerability.

Defensive priority

High

Recommended defensive actions

  • Review and apply the provided patches to the Linux kernel
  • Update to a fixed version of the Linux kernel
  • Monitor for potential exploitation attempts
  • Perform a thorough review of the system for any suspicious activity
  • 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.

Evidence notes

The vulnerability is confirmed by the Linux kernel maintainers, who have provided a patch to fix the issue. The affected versions of the Linux kernel are identified, and the fix is included in specific commits.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-74310 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-74310 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

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

Supplemental references

  • vhost/net: complete zerocopy ubufs only once

    Unverified legacy reference

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

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

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

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/6445b945024f4c7675ae5352b2d5885cb1deea71

    Supplemental source

  • Source reference

    Unverified legacy reference

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

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/321c73baf54d971ce3771fea275c98a247f7ee35

    Supplemental source

  • Source reference

    Unverified legacy reference

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

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/8f6898fe80794f2d7c3d38c1158c806e4074a1c4

    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.