---
id: CVE-2026-74709
title: |-
  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
summary: |-
  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 therefor…
severity: none
published: '2026-08-22'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T13:10:00.187'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-74709'
references:
  - url: 'https://git.kernel.org/stable/c/0ba2e1eb07a826d021344e2f146b6716c58139eb'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/9f60a67df8d3c862503bee62bada8e7089cba438'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/eb4c613d4ebc3f664e70d572b8867ba114a8754e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00206
epssPercentile: 0.09926
ingestedAt: '2026-10-14T13:30:58.544Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.