CVE-2026-64217

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

netfs: Fix overrun check in netfs_extract_user_iter()

Fix netfs_extract_user_iter() so that if iov_iter_extract_pages() overfills pages[], then those pages don't get included in the iterator constructed at the end of the function. If there was an overfill, memory corruption has already happened.

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
3%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 11, 2026

Advisory Details (5)

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

netfs: Fix overrun check in netfs_extract_user_iter() - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfs: Fix overrun check in netfs_extract_user_iter() - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfs: Fix overrun check in netfs_extract_user_iter() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96cc3beb2390ba9f9c128c5733c0ccfe450dd4f9
generic

netfs: Fix overrun check in netfs_extract_user_iter() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ef37eef83fad3542ee06db2940433ae1a92b39d
generic

netfs: Fix overrun check in netfs_extract_user_iter() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00efe58bbdcc93272d579ca24bfc912563f4a204

Vendor Advisories for CVE-2026-64217(1)

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

Patch Availability(3)

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

(2 across 2 ecosystems)
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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-64217?
CVE-2026-64217 is a high vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: netfs: Fix overrun check in netfsextractuser_iter() Fix netfsextractuseriter() so that if ioviterextractpages() overfills pages[], then those pages don't get included in the iterator constructed at the end of the function. If there…
When was CVE-2026-64217 disclosed?
CVE-2026-64217 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64217 actively exploited?
CVE-2026-64217 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 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64217?
CVE-2026-64217 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64217, 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-64217

Explore →

Is Your Infrastructure Affected by CVE-2026-64217?

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