CVE-2026-72408

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreHIGH confidence

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

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

geneve: gate GRO hint in geneve_gro_complete() on gs->gro_hint

geneve_gro_receive() reads the GRO hint through geneve_sk_gro_hint_off(), which honours it only when the socket enabled IFLA_GENEVE_GRO_HINT (gs->gro_hint). geneve_gro_complete() instead calls the low-level geneve_opt_gro_hint_off() and acts on the hint unconditionally.

On a tunnel without the hint, receive aggregates the frames as plain ETH_P_TEB while complete still honours an attacker-supplied hint option: it inflates gh_len by gro_hint->nested_hdr_len (u8) and redirects the dispatch type, so the inner gro_complete handler runs at nhoff + gh_len, an offset receive never pulled nor validated, reading out of bounds of the skb head:

BUG: KASAN: slab-out-of-bounds in ipv6_gro_complete (net/ipv6/ip6_offload.c:196) Read of size 1 at addr ffff88800fe91980 by task exploit/153 ipv6_gro_complete (net/ipv6/ip6_offload.c:196) geneve_gro_complete (drivers/net/geneve.c:965) udp_gro_complete (net/ipv4/udp_offload.c:940) inet_gro_complete (net/ipv4/af_inet.c:1621) __gro_flush (net/core/gro.c:306)

Gate the complete path on gs->gro_hint too via geneve_sk_gro_hint_off(), so both paths agree. Tunnels that enable the hint are unaffected.

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

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (2)

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

geneve: gate GRO hint in geneve_gro_complete() on gs->gro_hint - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49c2e7c0a69999a75ef5eaebe1559a20d0b3c15a
generic

geneve: gate GRO hint in geneve_gro_complete() on gs->gro_hint - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2651c174445884ac9e85622aeade9c1f7b98d8e5

Vendor Advisories for CVE-2026-72408(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 50× in last 7d / 50× 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-21 05:01 UTCGHSA enrichment
  2. 2026-08-21 01:16 UTCEG score recompute
  3. 2026-08-21 01:16 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 21:32 UTCGHSA enrichment
  6. 2026-08-20 17:48 UTCGHSA enrichment
  7. 2026-08-20 14:04 UTCGHSA enrichment
  8. 2026-08-20 10:20 UTCGHSA enrichment
  9. 2026-08-20 06:36 UTCGHSA enrichment
  10. 2026-08-20 02:51 UTCGHSA enrichment
  11. 2026-08-19 23:06 UTCGHSA enrichment
  12. 2026-08-19 19:22 UTCEG score recompute
  13. 2026-08-19 19:22 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 15:34 UTCGHSA enrichment
  16. 2026-08-19 11:44 UTCGHSA enrichment
  17. 2026-08-19 07:59 UTCGHSA enrichment
  18. 2026-08-19 04:15 UTCGHSA enrichment
  19. 2026-08-19 00:31 UTCGHSA enrichment
  20. 2026-08-18 20:44 UTCGHSA enrichment
  21. 2026-08-18 17:00 UTCEG score recompute
  22. 2026-08-18 17:00 UTCGHSA enrichment
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 12:40 UTCGHSA enrichment
Show 25 more
  1. 2026-08-18 08:43 UTCGHSA enrichment
  2. 2026-08-18 04:59 UTCGHSA enrichment
  3. 2026-08-18 01:14 UTCGHSA enrichment
  4. 2026-08-17 21:28 UTCGHSA enrichment
  5. 2026-08-17 17:44 UTCGHSA enrichment
  6. 2026-08-17 13:56 UTCEG score recompute
  7. 2026-08-17 13:56 UTCGHSA enrichment
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 10:12 UTCEG score recompute
  10. 2026-08-17 10:12 UTCGHSA enrichment
  11. 2026-08-17 06:29 UTCEG score recompute
  12. 2026-08-17 06:28 UTCGHSA enrichment
  13. 2026-08-17 05:57 UTCEG score recompute▲ 10.00
  14. 2026-08-17 05:57 UTCGHSA enrichment
  15. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 10 · severity → CRITICAL
  16. 2026-08-17 05:29 UTCEG score recompute
  17. 2026-08-17 05:29 UTCGHSA enrichment
  18. 2026-08-17 05:24 UTCMITRE cvelistV5
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 02:15 UTCEPSS rescore
  22. 2026-08-15 06:34 UTCGHSA enrichment
  23. 2026-08-15 06:23 UTCNVD update
  24. 2026-08-15 06:05 UTCEG score recompute
  25. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72408?
CVE-2026-72408 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: geneve: gate GRO hint in genevegrocomplete() on gs->gro_hint genevegroreceive() reads the GRO hint through geneveskgrohintoff(), which honours it only when the socket enabled IFLAGENEVEGRO_HINT (gs->grohint). genevegro_complete()…
When was CVE-2026-72408 disclosed?
CVE-2026-72408 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72408 actively exploited?
CVE-2026-72408 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 65.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72408?
CVE-2026-72408 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-72408?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72408, 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-72408

Explore →

Is Your Infrastructure Affected by CVE-2026-72408?

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

Start Free Scan →Browse All CVEs