CVE-2026-64577

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

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

gtp: check skb_pull_data() return in gtp1u_send_echo_resp()

gtp1u_send_echo_resp() ignores skb_pull_data()'s return value. Its caller gtp1u_udp_encap_recv() only guarantees 16 bytes (udphdr + gtp1_header), but the pull requests 20 (gtp1_header_long + udphdr). For a 16-19 byte echo request the pull fails and returns NULL without advancing skb->data; execution continues, and the following skb_push() plus the IP header pushed by iptunnel_xmit() move skb->data below skb->head, tripping skb_under_panic().

Fix it by dropping the packet when skb_pull_data() fails.

skbuff: skb_under_panic: ... kernel BUG at net/core/skbuff.c:214! Call Trace: skb_push (net/core/skbuff.c:2648) iptunnel_xmit (net/ipv4/ip_tunnel_core.c:82) gtp_encap_recv (drivers/net/gtp.c:701 drivers/net/gtp.c:808 drivers/net/gtp.c:920) udp_queue_rcv_one_skb (net/ipv4/udp.c:2388) ... Kernel panic - not syncing: Fatal exception in interrupt

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

gtp: check skb_pull_data() return in gtp1u_send_echo_resp() - kernel/git/stable/linux.git - Linux kernel stable tree

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

gtp: check skb_pull_data() return in gtp1u_send_echo_resp() - kernel/git/stable/linux.git - Linux kernel stable tree

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

gtp: check skb_pull_data() return in gtp1u_send_echo_resp() - kernel/git/stable/linux.git - Linux kernel stable tree

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

gtp: check skb_pull_data() return in gtp1u_send_echo_resp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/961e9b1e33445f8e42859ecc020c9f60d8b69a8b
generic

gtp: check skb_pull_data() return in gtp1u_send_echo_resp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4fc7923871d176ce0e5fecf4a9b7bb915af790ed

Vendor Advisories for CVE-2026-64577(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (338 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)6.12.101-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.6-1

Data Freshness Timeline

(refreshed 44× in last 7d / 84× 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-20 22:55 UTCEPSS rescore
  2. 2026-08-20 16:49 UTCVendor advisory
  3. 2026-08-20 16:49 UTCGHSA enrichment
  4. 2026-08-20 05:03 UTCGHSA enrichment
  5. 2026-08-19 17:26 UTCEG score recompute
  6. 2026-08-19 17:26 UTCVendor advisory
  7. 2026-08-19 17:26 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 16:56 UTCEG score recompute
  10. 2026-08-19 16:56 UTCVendor advisory
  11. 2026-08-19 16:56 UTCGHSA enrichment
  12. 2026-08-19 05:51 UTCVendor advisory
  13. 2026-08-19 05:51 UTCGHSA enrichment
  14. 2026-08-18 18:15 UTCEG score recompute
  15. 2026-08-18 18:15 UTCVendor advisory
  16. 2026-08-18 18:15 UTCGHSA enrichment
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-18 04:58 UTCGHSA enrichment
  19. 2026-08-17 17:22 UTCEG score recompute
  20. 2026-08-17 17:22 UTCVendor advisory
  21. 2026-08-17 17:22 UTCGHSA enrichment
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-17 05:42 UTCEG score recompute
  24. 2026-08-17 05:42 UTCVendor advisory
  25. 2026-08-17 05:42 UTCGHSA enrichment
Show 59 more
  1. 2026-08-17 05:13 UTCEG score recompute
  2. 2026-08-17 05:13 UTCVendor advisory
  3. 2026-08-17 05:13 UTCGHSA enrichment
  4. 2026-08-16 20:36 UTCEG score recompute
  5. 2026-08-16 20:36 UTCVendor advisory
  6. 2026-08-16 20:36 UTCGHSA enrichment
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 08:59 UTCEG score recompute
  9. 2026-08-16 08:59 UTCVendor advisory
  10. 2026-08-16 08:59 UTCGHSA enrichment
  11. 2026-08-15 21:23 UTCVendor advisory
  12. 2026-08-15 21:23 UTCGHSA enrichment
  13. 2026-08-15 09:47 UTCEG score recompute
  14. 2026-08-15 09:47 UTCVendor advisory
  15. 2026-08-15 09:47 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 22:10 UTCVendor advisory
  18. 2026-08-14 22:10 UTCGHSA enrichment
  19. 2026-08-14 10:34 UTCGHSA enrichment
  20. 2026-08-13 22:57 UTCEG score recompute
  21. 2026-08-13 22:57 UTCVendor advisory
  22. 2026-08-13 22:57 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 11:21 UTCVendor advisory
  25. 2026-08-13 11:21 UTCGHSA enrichment
  26. 2026-08-12 23:44 UTCEG score recompute
  27. 2026-08-12 23:44 UTCGHSA enrichment
  28. 2026-08-12 13:51 UTCEPSS rescore
  29. 2026-08-12 12:08 UTCVendor advisory
  30. 2026-08-12 12:08 UTCGHSA enrichment
  31. 2026-08-12 00:30 UTCEG score recompute
  32. 2026-08-12 00:30 UTCVendor advisory
  33. 2026-08-12 00:30 UTCGHSA enrichment
  34. 2026-08-11 12:54 UTCVendor advisory
  35. 2026-08-11 12:54 UTCGHSA enrichment
  36. 2026-08-11 01:18 UTCEG score recompute
  37. 2026-08-11 01:18 UTCVendor advisory
  38. 2026-08-11 01:18 UTCGHSA enrichment
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-10 13:42 UTCVendor advisory
  41. 2026-08-10 13:42 UTCGHSA enrichment
  42. 2026-08-10 02:05 UTCGHSA enrichment
  43. 2026-08-09 14:29 UTCEG score recompute
  44. 2026-08-09 14:29 UTCVendor advisory
  45. 2026-08-09 14:29 UTCGHSA enrichment
  46. 2026-08-09 13:47 UTCEPSS rescore
  47. 2026-08-09 02:53 UTCEG score recompute
  48. 2026-08-09 02:53 UTCGHSA enrichment
  49. 2026-08-08 15:17 UTCEG score recompute 7.50
  50. 2026-08-08 15:17 UTCGHSA enrichment
  51. 2026-08-08 15:16 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  52. 2026-08-08 02:14 UTCEG score recompute
  53. 2026-08-08 02:14 UTCGHSA enrichment
  54. 2026-08-06 13:47 UTCEPSS rescore
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-05 08:20 UTCNVD update
  58. 2026-08-05 08:12 UTCEG score recompute
  59. 2026-08-05 08:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64577?
CVE-2026-64577 is a high vulnerability published on August 5, 2026. In the Linux kernel, the following vulnerability has been resolved: gtp: check skbpulldata() return in gtp1usendecho_resp() gtp1usendechoresp() ignores skbpull_data()'s return value. Its caller gtp1uudpencap_recv() only guarantees 16 bytes (udphdr + gtp1header), but the pull requests 20…
When was CVE-2026-64577 disclosed?
CVE-2026-64577 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64577 actively exploited?
CVE-2026-64577 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64577?
CVE-2026-64577 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-64577?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64577, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64577

Explore →

Is Your Infrastructure Affected by CVE-2026-64577?

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