CVE-2026-74709

xsk: clear metadata pointer when no timestamp is requested

N/A
Published: August 22, 2026 at 03:33 PM UTC
Updated: October 14, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: xsk: clear metadata pointer when no timestamp is requested User space can change metadata flags after request processing. Rereading them during completion can therefore make the kernel write a timestamp that was not requested when the packet was submitted. Clear the metadata pointer during request processing unless timestamp completion is requested. Completion handling can then use the pointer itself instead of rereading the flags. On the mlx5 multi-packet WQE path metadata is evaluated per batch: xsk_tx_metadata_request() runs only for the descriptor that starts a session, just like the checksum offload that is applied once through the shared WQE. Only that descriptor's pointer is reset, so completion handling can record a timestamp for the other descriptors of the session regardless of their own XDP_TXMD_FLAGS_TIMESTAMP bit. The write stays inside the metadata area; the single-WQE, other zero-copy, and generic paths reset the pointer per descriptor and are unaffected.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.14.2 ≤ v < 6.156.14.26.15ca4419f15abd19ba8be1e109661b60f9f5b6c9f0d9d736c416c9a85f84e15435ba82a177262e745b
Vendor states this is fixed in 0ba2e1eb07a826d021344e2f146b6716c58139eb (fixed)
Vendor states this is fixed in 9f60a67df8d3c862503bee62bada8e7089cba438 (fixed)
Vendor states this is fixed in eb4c613d4ebc3f664e70d572b8867ba114a8754e (fixed)
Vendor states this is fixed in 6.15 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 7.1.9 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card