Answer in brief
CVE-2026-74709 records a Unknown severity vulnerability in xsk: clear metadata pointer when no timestamp is requested. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 <0ba2e1eb07a826d021344e2f146b6716c58139eb || >=ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 <eb4c613d4ebc3f664e70d572b8867ba114a8754e || >=ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 <9f60a67df8d3c862503bee62bada8e7089cba438 || d9d736c416c9a85f84e15435ba82a177262e745b || >=6.14.2 <6.15 | 0ba2e1eb07a826d021344e2f146b6716c58139eb, eb4c613d4ebc3f664e70d572b8867ba114a8754e, 9f60a67df8d3c862503bee62bada8e7089cba438, 6.15 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 22, 2026
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.
Quoted source text, attributed separately from HOL analysis.