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.
Published: 2026-08-22
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: kernel data corruption via unintended timestamp injection
Action: Apply patch
AI Analysis

Impact

The Linux kernel’s XSK subsystem contains a flaw that allows user‑space to modify packet metadata flags after the kernel has finished staging a packet. Because the kernel later re‑evaluates those same flags during the completion phase, it can mistakenly write a timestamp into the metadata even when the caller did not request one. This unintended timestamp alters the packet’s metadata buffer, creating kernel data corruption that can result in unstable kernel operation or other disruptive behavior.

Affected Systems

All unpatched Linux kernel releases that include the XSK subsystem are affected. The issue is most pronounced in the mlx5 multi‑packet WQE path, where only the descriptor that starts a session clears its metadata pointer, allowing subsequent descriptors to be timestamped regardless of their own XDP_TXMD_FLAGS_TIMESTAMP setting. Therefore any Linux system running a kernel version without the patch to clear the metadata pointer during request processing is vulnerable.

Risk and Exploitability

The CVSS score of 5.5 indicates a medium severity, while the EPSS score of < 1% suggests a low probability of exploitation. The vulnerability is not listed in CISA’s KEV catalog. The likely attack vector is local or privileged access, as the adversary must manipulate XDP‑enabled packets and modify metadata flags after submission. No public exploits are known, but the potential for kernel data corruption or disruptive behavior raises the risk to medium if an attacker can exercise that local access.

Generated by OpenCVE AI on August 25, 2026 at 16:26 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that includes the patch which clears the metadata pointer when no timestamp is requested.
  • If an immediate kernel upgrade is not feasible, temporarily disable XDP or restrict the use of metadata flags that can be altered after a request has been queued, such as by disabling packet timestamping or applying stricter metadata validation.
  • Continuously monitor system logs and network traffic for unexpected timestamp entries or anomalies in packet metadata until the kernel patch is applied.

Generated by OpenCVE AI on August 25, 2026 at 16:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 25 Aug 2026 15:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Tue, 25 Aug 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-367
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low


Sat, 22 Aug 2026 19:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Sat, 22 Aug 2026 15:45:00 +0000

Type Values Removed Values Added
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.
Title xsk: clear metadata pointer when no timestamp is requested
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-22T15:33:06.558Z

Reserved: 2026-08-15T05:44:03.927Z

Link: CVE-2026-74709

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-22T16:16:45.640

Modified: 2026-08-22T16:16:45.640

Link: CVE-2026-74709

cve-icon Redhat

Severity : Low

Publid Date: 2026-08-22T00:00:00Z

Links: CVE-2026-74709 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-25T16:30:06Z

Weaknesses
  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition