CVE-2026-74707

Unknown

Last modified

CVE-2026-74707 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: xsk: validate metadata when processing requests The zero-copy path validates TX metadata while obtaining the descriptor context, then reads it again later when preparing the hardware request. User space can change the metadata between those operations and bypass the original validation. Validate the metadata in xsk_tx_metadata_request() and use the resulting flags snapshot for every feature check. Read request fields once so all zero-copy drivers process only values observed after successful validation..

Description

In the Linux kernel, the following vulnerability has been resolved: xsk: validate metadata when processing requests The zero-copy path validates TX metadata while obtaining the descriptor context, then reads it again later when preparing the hardware request. User space can change the metadata between those operations and bypass the original validation. Validate the metadata in xsk_tx_metadata_request() and use the resulting flags snapshot for every feature check. Read request fields once so all zero-copy drivers process only values observed after successful validation.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ca4419f15abd19ba8be1e109661b60f9f5b6c9f0, < 5fd121971912dee2f5af1efec64462ac722deb17; >= ca4419f15abd19ba8be1e109661b60f9f5b6c9f0, < 0cc7aa6e0d19027fdd42e6fbd156267ac1e3bbba; >= ca4419f15abd19ba8be1e109661b60f9f5b6c9f0, < 849b1664dbda1cf6c63e0fd4f9dec23782b8c851; d9d736c416c9a85f84e15435ba82a177262e745b; >= 6.14.2, < 6.15
LinuxLinux6.15

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74707?
In the Linux kernel, the following vulnerability has been resolved: xsk: validate metadata when processing requests The zero-copy path validates TX metadata while obtaining the descriptor context, then reads it again later when preparing the hardware request. User space can change the metadata between those operations and bypass the original validation. Validate the metadata in xsk_tx_metadata_request() and use the resulting flags snapshot for every feature check. Read request fields once so all zero-copy drivers process only values observed after successful validation.
How severe is CVE-2026-74707?
Severity scoring for CVE-2026-74707 is pending analysis.
How do I fix CVE-2026-74707?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-74707?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST