CVE-2026-64422

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.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: 7.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: ipv4: bound TCP reordering sysctl writes and MTU probe sizes

Reject invalid net.ipv4.tcp_reordering values before they reach TCP socket state. The sysctl is stored as an int but copied into the u32 tp->reordering field for new sockets, so negative writes wrap to large values.

With tcp_mtu_probing=2, the wrapped value can overflow the tcp_mtu_probe() size calculation and drive the MTU probing path into an out-of-bounds read. Route tcp_reordering writes through proc_dointvec_minmax() and require it to be at least 1. Also require tcp_max_reordering to be at least 1 so the configured maximum cannot become negative either.

When registering the table for a non-init network namespace, relocate extra2 pointers that refer into init_net.ipv4 so the tcp_reordering upper bound follows that namespace's tcp_max_reordering.

Harden tcp_mtu_probe() itself by computing size_needed as u64. This keeps the send queue and window checks from being bypassed through signed integer overflow.

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

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/99206ce2244f8a3ed64298d0667c9055845a5dc7
generic

net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/782708ca1ea1f68b8cbb5ea3a7f5f18d0000efae
generic

net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/27ddf4486c7dbf5bdd393fa8bef6b67179796d98

Vendor Advisories for CVE-2026-64422(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1

Data Freshness Timeline

(refreshed 30× in last 7d / 149× 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 177 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64422?
CVE-2026-64422 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes Reject invalid net.ipv4.tcp_reordering values before they reach TCP socket state. The sysctl is stored as an int but copied into the u32 tp->reordering field for new…
When was CVE-2026-64422 disclosed?
CVE-2026-64422 was first published in the National Vulnerability Database on July 25, 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-64422 actively exploited?
CVE-2026-64422 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64422?
CVE-2026-64422 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-64422?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64422, 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-64422

Explore →

Is Your Infrastructure Affected by CVE-2026-64422?

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