CVE-2026-74710

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

xsk: require at least 16 bytes of TX metadata

AF_XDP accepts a TX metadata length as small as eight bytes, but every supported request needs the flags plus at least one eight-byte request field. Such short metadata also lets the kernel read beyond the registered area.

Require 16 bytes rather than sizeof(struct xsk_tx_metadata) to preserve compatibility with applications that do not use launch-time metadata.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
No patch confirmed yet.
generic

xsk: require at least 16 bytes of TX metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1bb30b181d9f0484e141f8411e15ed906d5c6780
generic

xsk: require at least 16 bytes of TX metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cfb9d2976b277e554e28c165e3eff4b4a8ea10bd
generic

xsk: require at least 16 bytes of TX metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/642c6e73fce17fdca93a5793c4d22359fda866d7
generic

xsk: require at least 16 bytes of TX metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21b8536aee819792f1b4b38b9aacf2a073025d49

Vendor Advisories for CVE-2026-74710(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 25× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 03:15 UTCEG score recompute
  2. 2026-08-30 03:15 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 14:17 UTCGHSA enrichment
  5. 2026-08-29 01:16 UTCEG score recompute
  6. 2026-08-29 01:16 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 12:13 UTCGHSA enrichment
  9. 2026-08-27 23:16 UTCEG score recompute
  10. 2026-08-27 23:16 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 10:19 UTCGHSA enrichment
  13. 2026-08-26 21:21 UTCEG score recompute
  14. 2026-08-26 21:21 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 08:24 UTCGHSA enrichment
  17. 2026-08-25 19:26 UTCEG score recompute
  18. 2026-08-25 19:26 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 06:29 UTCEG score recompute
  21. 2026-08-25 06:29 UTCGHSA enrichment
  22. 2026-08-25 05:55 UTCEG score recompute 7.80
  23. 2026-08-25 05:55 UTCGHSA enrichment
  24. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  25. 2026-08-24 14:18 UTCEPSS rescore
Show 3 more
  1. 2026-08-22 16:24 UTCNVD update
  2. 2026-08-22 15:38 UTCEG score recompute
  3. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74710?
CVE-2026-74710 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: xsk: require at least 16 bytes of TX metadata AF_XDP accepts a TX metadata length as small as eight bytes, but every supported request needs the flags plus at least one eight-byte request field. Such short metadata also lets the…
When was CVE-2026-74710 disclosed?
CVE-2026-74710 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74710 actively exploited?
CVE-2026-74710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-74710?
CVE-2026-74710 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74710, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74710

Explore →

Is Your Infrastructure Affected by CVE-2026-74710?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.