{"api_version":"1","generated_at":"2026-08-22T21:53:02+00:00","cve":"CVE-2026-74709","urls":{"html":"https://cve.report/CVE-2026-74709","api":"https://cve.report/api/cve/CVE-2026-74709.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74709","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74709"},"summary":{"title":"xsk: clear metadata pointer when no timestamp is requested","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxsk: clear metadata pointer when no timestamp is requested\n\nUser space can change metadata flags after request processing. Rereading\nthem during completion can therefore make the kernel write a timestamp\nthat was not requested when the packet was submitted.\n\nClear the metadata pointer during request processing unless timestamp\ncompletion is requested. Completion handling can then use the pointer\nitself instead of rereading the flags.\n\nOn the mlx5 multi-packet WQE path metadata is evaluated per batch:\nxsk_tx_metadata_request() runs only for the descriptor that starts a\nsession, just like the checksum offload that is applied once through the\nshared WQE. Only that descriptor's pointer is reset, so completion\nhandling can record a timestamp for the other descriptors of the session\nregardless of their own XDP_TXMD_FLAGS_TIMESTAMP bit. The write stays\ninside the metadata area; the single-WQE, other zero-copy, and generic\npaths reset the pointer per descriptor and are unaffected.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-22 16:16:45","updated_at":"2026-08-22 16:16:45"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/0ba2e1eb07a826d021344e2f146b6716c58139eb","name":"https://git.kernel.org/stable/c/0ba2e1eb07a826d021344e2f146b6716c58139eb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9f60a67df8d3c862503bee62bada8e7089cba438","name":"https://git.kernel.org/stable/c/9f60a67df8d3c862503bee62bada8e7089cba438","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/eb4c613d4ebc3f664e70d572b8867ba114a8754e","name":"https://git.kernel.org/stable/c/eb4c613d4ebc3f664e70d572b8867ba114a8754e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74709","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74709","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 0ba2e1eb07a826d021344e2f146b6716c58139eb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 eb4c613d4ebc3f664e70d572b8867ba114a8754e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ca4419f15abd19ba8be1e109661b60f9f5b6c9f0 9f60a67df8d3c862503bee62bada8e7089cba438 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d9d736c416c9a85f84e15435ba82a177262e745b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.14.2 6.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.45 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.9 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["include/net/xdp_sock.h","net/xdp/xsk.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"0ba2e1eb07a826d021344e2f146b6716c58139eb","status":"affected","version":"ca4419f15abd19ba8be1e109661b60f9f5b6c9f0","versionType":"git"},{"lessThan":"eb4c613d4ebc3f664e70d572b8867ba114a8754e","status":"affected","version":"ca4419f15abd19ba8be1e109661b60f9f5b6c9f0","versionType":"git"},{"lessThan":"9f60a67df8d3c862503bee62bada8e7089cba438","status":"affected","version":"ca4419f15abd19ba8be1e109661b60f9f5b6c9f0","versionType":"git"},{"status":"affected","version":"d9d736c416c9a85f84e15435ba82a177262e745b","versionType":"git"},{"lessThan":"6.15","status":"affected","version":"6.14.2","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["include/net/xdp_sock.h","net/xdp/xsk.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.15"},{"lessThan":"6.15","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.45","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.9","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.45","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.9","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.14.2","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nxsk: clear metadata pointer when no timestamp is requested\n\nUser space can change metadata flags after request processing. Rereading\nthem during completion can therefore make the kernel write a timestamp\nthat was not requested when the packet was submitted.\n\nClear the metadata pointer during request processing unless timestamp\ncompletion is requested. Completion handling can then use the pointer\nitself instead of rereading the flags.\n\nOn the mlx5 multi-packet WQE path metadata is evaluated per batch:\nxsk_tx_metadata_request() runs only for the descriptor that starts a\nsession, just like the checksum offload that is applied once through the\nshared WQE. Only that descriptor's pointer is reset, so completion\nhandling can record a timestamp for the other descriptors of the session\nregardless of their own XDP_TXMD_FLAGS_TIMESTAMP bit. The write stays\ninside the metadata area; the single-WQE, other zero-copy, and generic\npaths reset the pointer per descriptor and are unaffected."}],"providerMetadata":{"dateUpdated":"2026-08-22T15:33:06.558Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/0ba2e1eb07a826d021344e2f146b6716c58139eb"},{"url":"https://git.kernel.org/stable/c/eb4c613d4ebc3f664e70d572b8867ba114a8754e"},{"url":"https://git.kernel.org/stable/c/9f60a67df8d3c862503bee62bada8e7089cba438"}],"title":"xsk: clear metadata pointer when no timestamp is requested","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74709","datePublished":"2026-08-22T15:33:06.558Z","dateReserved":"2026-08-15T05:44:03.927Z","dateUpdated":"2026-08-22T15:33:06.558Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-22 16:16:45","lastModifiedDate":"2026-08-22 16:16:45","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74709","Ordinal":"1","Title":"xsk: clear metadata pointer when no timestamp is requested","CVE":"CVE-2026-74709","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74709","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nxsk: clear metadata pointer when no timestamp is requested\n\nUser space can change metadata flags after request processing. Rereading\nthem during completion can therefore make the kernel write a timestamp\nthat was not requested when the packet was submitted.\n\nClear the metadata pointer during request processing unless timestamp\ncompletion is requested. Completion handling can then use the pointer\nitself instead of rereading the flags.\n\nOn the mlx5 multi-packet WQE path metadata is evaluated per batch:\nxsk_tx_metadata_request() runs only for the descriptor that starts a\nsession, just like the checksum offload that is applied once through the\nshared WQE. Only that descriptor's pointer is reset, so completion\nhandling can record a timestamp for the other descriptors of the session\nregardless of their own XDP_TXMD_FLAGS_TIMESTAMP bit. The write stays\ninside the metadata area; the single-WQE, other zero-copy, and generic\npaths reset the pointer per descriptor and are unaffected.","Type":"Description","Title":"xsk: clear metadata pointer when no timestamp is requested"}]}}}