CVE-2026-74709
Last modified
CVE-2026-74709 is a vulnerability of currently unknown severity. 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.
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= ca4419f15abd19ba8be1e109661b60f9f5b6c9f0, < 0ba2e1eb07a826d021344e2f146b6716c58139eb; >= ca4419f15abd19ba8be1e109661b60f9f5b6c9f0, < eb4c613d4ebc3f664e70d572b8867ba114a8754e; >= ca4419f15abd19ba8be1e109661b60f9f5b6c9f0, < 9f60a67df8d3c862503bee62bada8e7089cba438; d9d736c416c9a85f84e15435ba82a177262e745b; >= 6.14.2, < 6.15 |
| Linux | Linux | 6.15 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-74709?
How severe is CVE-2026-74709?
How do I fix CVE-2026-74709?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-74703In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74704In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74705In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74706In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74707In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74708In the Linux kernel, the following vulnerability has been re…
- CVE-2026-7471GitLab has remediated an issue in GitLab EE affecting all ve…3.5
- CVE-2026-74710In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74711In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74712In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74713In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74714In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-74709?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
