xsk: clear metadata pointer when no timestamp is requested
Summary
| CVE | CVE-2026-74709 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-22 16:16:45 UTC |
| Updated | 2026-08-22 16:16:45 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 0ba2e1eb07a826d021344e2f146b6716c58139eb git |
Not specified |
| CNA |
Linux |
Linux |
affected ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 eb4c613d4ebc3f664e70d572b8867ba114a8754e git |
Not specified |
| CNA |
Linux |
Linux |
affected ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 9f60a67df8d3c862503bee62bada8e7089cba438 git |
Not specified |
| CNA |
Linux |
Linux |
affected d9d736c416c9a85f84e15435ba82a177262e745b git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.14.2 6.15 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.15 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.15 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.45 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.9 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/0ba2e1eb07a826d021344e2f146b6716c58139eb |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9f60a67df8d3c862503bee62bada8e7089cba438 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/eb4c613d4ebc3f664e70d572b8867ba114a8754e |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.