CVE-2026-64009

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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

A fix is available — apply it.

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

xfrm: Check for underflow in xfrm_state_mtu

Leo Lin reported OOB write issue in esp component:

xfrm_state_mtu() returns u32 but performs its arithmetic in unsigned modulo-2^32 space using an attacker-influenced "header_len + authsize + net_adj" subtracted from a small "mtu" argument. A nobody user can install an IPv4 ESP tunnel SA with a large authentication key (XFRMA_ALG_AUTH_TRUNC, e.g. hmac(sha512), 64-byte key, 64-byte trunc), configure a small interface MTU (68 bytes), and set XFRMA_TFCPAD to a large value. When a single UDP datagram is then sent through the tunnel, xfrm_state_mtu() underflows to a near-2^32 value, and esp_output() consumes it as a signed int via:

padto = min(x->tfcpad, xfrm_state_mtu(x, mtu_cached)) esp.tfclen = padto - skb->len (assigned to int)

esp.tfclen ends up negative (e.g. -207). It is sign-extended to size_t when passed to memset() inside esp_output_fill_trailer(), producing a ~16 EB write of zeroes at skb_tail_pointer(skb). KASAN logs it as "Write of size 18446744073709551537 at addr ffff888...".

Check for underflow and return 1. This causes the sendmsg attempt to fail with ENETUNREACH.

CVSS v3
7.8
EG Score
7.8(medium)
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
4%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

xfrm: Check for underflow in xfrm_state_mtu - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfrm: Check for underflow in xfrm_state_mtu - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/82ac903e0b519849647657b8c48d21237ada06a2
generic

xfrm: Check for underflow in xfrm_state_mtu - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/820e501be8aee4b365d218d83227b314309c5fda
generic

xfrm: Check for underflow in xfrm_state_mtu - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8014f70c4e6e5ab101ae3860a614e65e988372e3
generic

xfrm: Check for underflow in xfrm_state_mtu - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/742b04d0550b0ec89dcbc99537ec88653bd1ad90
generic

xfrm: Check for underflow in xfrm_state_mtu - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3db50ceeacb52806d8fe86fb1dfe944df0b9f789
generic

xfrm: Check for underflow in xfrm_state_mtu - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a41b1b31c61c52b972278ce1732a1443f5e89ed
generic

xfrm: Check for underflow in xfrm_state_mtu - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1021d2877b689a648b27815c854557a917122e93

Vendor Advisories for CVE-2026-64009(1)

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

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 30× in last 7d / 161× 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.

Showing the most recent 100 of 207 total refreshes for this CVE.

  1. 2026-08-30 02:52 UTCEG score recompute
  2. 2026-08-30 02:52 UTCVendor advisory
  3. 2026-08-30 02:52 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 23:48 UTCEG score recompute
  7. 2026-08-27 23:48 UTCVendor advisory
  8. 2026-08-27 23:48 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 11:52 UTCVendor advisory
  11. 2026-08-27 11:51 UTCGHSA enrichment
  12. 2026-08-26 22:23 UTCEG score recompute
  13. 2026-08-26 22:23 UTCVendor advisory
  14. 2026-08-26 22:23 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 07:24 UTCVendor advisory
  17. 2026-08-26 07:24 UTCGHSA enrichment
  18. 2026-08-25 18:47 UTCGHSA enrichment
  19. 2026-08-25 07:00 UTCVendor advisory
  20. 2026-08-25 07:00 UTCGHSA enrichment
  21. 2026-08-24 19:23 UTCEG score recompute
  22. 2026-08-24 19:23 UTCVendor advisory
  23. 2026-08-24 19:23 UTCGHSA enrichment
  24. 2026-08-24 07:46 UTCVendor advisory
  25. 2026-08-24 07:46 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 19:56 UTCVendor advisory
  2. 2026-08-23 19:56 UTCGHSA enrichment
  3. 2026-08-23 08:20 UTCEG score recompute
  4. 2026-08-23 08:20 UTCVendor advisory
  5. 2026-08-23 08:20 UTCGHSA enrichment
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 20:43 UTCVendor advisory
  8. 2026-08-22 20:43 UTCGHSA enrichment
  9. 2026-08-22 09:06 UTCEG score recompute
  10. 2026-08-22 09:06 UTCVendor advisory
  11. 2026-08-22 09:06 UTCGHSA enrichment
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 21:29 UTCVendor advisory
  14. 2026-08-21 21:29 UTCGHSA enrichment
  15. 2026-08-21 09:53 UTCEG score recompute
  16. 2026-08-21 09:53 UTCVendor advisory
  17. 2026-08-21 09:53 UTCGHSA enrichment
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 22:16 UTCVendor advisory
  20. 2026-08-20 22:16 UTCGHSA enrichment
  21. 2026-08-20 10:40 UTCVendor advisory
  22. 2026-08-20 10:40 UTCGHSA enrichment
  23. 2026-08-19 23:03 UTCEG score recompute
  24. 2026-08-19 23:03 UTCVendor advisory
  25. 2026-08-19 23:02 UTCGHSA enrichment
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 07:25 UTCVendor advisory
  28. 2026-08-19 07:25 UTCGHSA enrichment
  29. 2026-08-18 19:48 UTCEG score recompute
  30. 2026-08-18 19:48 UTCVendor advisory
  31. 2026-08-18 19:48 UTCGHSA enrichment
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-18 03:41 UTCVendor advisory
  34. 2026-08-18 03:41 UTCGHSA enrichment
  35. 2026-08-17 15:44 UTCEG score recompute
  36. 2026-08-17 15:44 UTCVendor advisory
  37. 2026-08-17 15:44 UTCGHSA enrichment
  38. 2026-08-17 13:47 UTCEPSS rescore
  39. 2026-08-17 04:08 UTCVendor advisory
  40. 2026-08-17 04:08 UTCGHSA enrichment
  41. 2026-08-16 16:32 UTCEG score recompute
  42. 2026-08-16 16:32 UTCVendor advisory
  43. 2026-08-16 16:32 UTCGHSA enrichment
  44. 2026-08-16 14:56 UTCEPSS rescore
  45. 2026-08-16 04:56 UTCEG score recompute
  46. 2026-08-16 04:56 UTCVendor advisory
  47. 2026-08-16 04:56 UTCGHSA enrichment
  48. 2026-08-15 17:20 UTCVendor advisory
  49. 2026-08-15 17:20 UTCGHSA enrichment
  50. 2026-08-15 05:43 UTCEG score recompute
  51. 2026-08-15 05:43 UTCVendor advisory
  52. 2026-08-15 05:43 UTCGHSA enrichment
  53. 2026-08-15 01:30 UTCEPSS rescore
  54. 2026-08-14 18:06 UTCVendor advisory
  55. 2026-08-14 18:06 UTCGHSA enrichment
  56. 2026-08-14 06:30 UTCEG score recompute
  57. 2026-08-14 06:30 UTCVendor advisory
  58. 2026-08-14 06:30 UTCGHSA enrichment
  59. 2026-08-13 22:00 UTCEPSS rescore
  60. 2026-08-13 18:53 UTCVendor advisory
  61. 2026-08-13 18:53 UTCGHSA enrichment
  62. 2026-08-13 07:17 UTCVendor advisory
  63. 2026-08-13 07:17 UTCGHSA enrichment
  64. 2026-08-12 19:28 UTCEG score recompute
  65. 2026-08-12 19:28 UTCVendor advisory
  66. 2026-08-12 19:28 UTCGHSA enrichment
  67. 2026-08-12 13:51 UTCEPSS rescore
  68. 2026-08-12 07:52 UTCVendor advisory
  69. 2026-08-12 07:52 UTCGHSA enrichment
  70. 2026-08-11 20:15 UTCEG score recompute
  71. 2026-08-11 20:15 UTCVendor advisory
  72. 2026-08-11 20:15 UTCGHSA enrichment
  73. 2026-08-11 08:39 UTCEG score recompute
  74. 2026-08-11 08:39 UTCVendor advisory
  75. 2026-08-11 08:39 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64009?
CVE-2026-64009 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: xfrm: Check for underflow in xfrmstatemtu Leo Lin reported OOB write issue in esp component: xfrmstatemtu() returns u32 but performs its arithmetic in unsigned modulo-2^32 space using an attacker-influenced "header_len + authsize +…
When was CVE-2026-64009 disclosed?
CVE-2026-64009 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64009 actively exploited?
CVE-2026-64009 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 96.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64009?
CVE-2026-64009 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64009?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64009, 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-64009

Explore →

Is Your Infrastructure Affected by CVE-2026-64009?

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