CVE-2026-74665

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: 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:

net: fix skb length accounting after generic XDP frag adjustment

Generic XDP exposes non-linear skb fragments through an xdp_buff. If an XDP program adjusts the fragment area, bpf_prog_run_generic_xdp() copies xdp_frags_size back to skb->data_len but leaves skb->len containing the old fragment contribution.

After a fragment shrink, this makes skb_headlen() larger than the actual linear area. In the reproduced UDP receive path, __skb_datagram_iter() copied 1024 bytes past the actual linear tail to userspace, starting at struct skb_shared_info. The copied bytes included the affected skb's nr_frags, xdp_frags_size and a kernel pointer from skb_shinfo(skb)->frags[0]. Real packet data was displaced by the same amount and truncated at the end.

Subtract the old data_len before replacing it and add the new data_len afterwards, keeping skb->len and skb->data_len synchronized.

A 60000-byte UDP datagram on a veth pair with MTU 64000 was shortened by 1024 bytes from its fragment area. Before the fix, all 10 runs produced corrupted payloads. After the fix, all 10 runs matched the expected payload exactly.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
46(Track)
EG Risk 46/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
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (4)

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

net: fix skb length accounting after generic XDP frag adjustment - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: fix skb length accounting after generic XDP frag adjustment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72468efcc089782fa047afddd10856b11a14ef5b
generic

net: fix skb length accounting after generic XDP frag adjustment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f30f9c302cea1f2ebf97abe574c1826544223d7
generic

net: fix skb length accounting after generic XDP frag adjustment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33f2b2eb33d666ecac68031e0f31424fb70528db

Vendor Advisories for CVE-2026-74665(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 46× in last 7d / 49× 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:42 UTCEG score recompute
  2. 2026-08-30 03:42 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 23:54 UTCGHSA enrichment
  5. 2026-08-29 20:06 UTCGHSA enrichment
  6. 2026-08-29 16:15 UTCGHSA enrichment
  7. 2026-08-29 12:26 UTCGHSA enrichment
  8. 2026-08-29 08:30 UTCGHSA enrichment
  9. 2026-08-29 04:40 UTCGHSA enrichment
  10. 2026-08-29 00:50 UTCEG score recompute
  11. 2026-08-29 00:49 UTCGHSA enrichment
  12. 2026-08-28 21:42 UTCEPSS rescore
  13. 2026-08-28 16:29 UTCGHSA enrichment
  14. 2026-08-28 11:57 UTCGHSA enrichment
  15. 2026-08-28 08:08 UTCGHSA enrichment
  16. 2026-08-28 04:18 UTCGHSA enrichment
  17. 2026-08-28 00:26 UTCGHSA enrichment
  18. 2026-08-27 20:34 UTCGHSA enrichment
  19. 2026-08-27 16:44 UTCEG score recompute
  20. 2026-08-27 16:43 UTCGHSA enrichment
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-27 12:54 UTCGHSA enrichment
  23. 2026-08-27 09:05 UTCGHSA enrichment
  24. 2026-08-27 05:16 UTCGHSA enrichment
  25. 2026-08-27 01:27 UTCGHSA enrichment
Show 24 more
  1. 2026-08-26 21:39 UTCGHSA enrichment
  2. 2026-08-26 17:51 UTCEG score recompute
  3. 2026-08-26 17:51 UTCGHSA enrichment
  4. 2026-08-26 14:47 UTCEPSS rescore
  5. 2026-08-26 13:14 UTCGHSA enrichment
  6. 2026-08-26 09:23 UTCGHSA enrichment
  7. 2026-08-26 05:23 UTCGHSA enrichment
  8. 2026-08-26 01:35 UTCGHSA enrichment
  9. 2026-08-25 21:47 UTCGHSA enrichment
  10. 2026-08-25 17:59 UTCGHSA enrichment
  11. 2026-08-25 14:10 UTCEG score recompute
  12. 2026-08-25 14:10 UTCGHSA enrichment
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-25 10:17 UTCEG score recompute
  15. 2026-08-25 10:17 UTCGHSA enrichment
  16. 2026-08-25 06:29 UTCEG score recompute
  17. 2026-08-25 06:29 UTCGHSA enrichment
  18. 2026-08-25 05:56 UTCEG score recompute 9.10
  19. 2026-08-25 05:56 UTCGHSA enrichment
  20. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  21. 2026-08-24 14:18 UTCEPSS rescore
  22. 2026-08-22 16:24 UTCNVD update
  23. 2026-08-22 15:41 UTCEG score recompute
  24. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74665?
CVE-2026-74665 is a critical vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: net: fix skb length accounting after generic XDP frag adjustment Generic XDP exposes non-linear skb fragments through an xdp_buff. If an XDP program adjusts the fragment area, bpfprogrungenericxdp() copies xdpfragssize back to…
When was CVE-2026-74665 disclosed?
CVE-2026-74665 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-74665 actively exploited?
CVE-2026-74665 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 69.9% of all scored CVEs.
What is the CVSS score of CVE-2026-74665?
CVE-2026-74665 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-74665?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74665, 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-74665

Explore →

Is Your Infrastructure Affected by CVE-2026-74665?

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