CVE-2026-64160

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.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: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

netfs: Fix potential for tearing in ->remote_i_size and ->zero_point

Fix potential tearing in using ->remote_i_size and ->zero_point by copying i_size_read() and i_size_write() and using the same seqcount as for i_size.

We need to make sure that netfslib and the filesystems that use it always hold i_lock whilst updating any of the sizes to prevent i_size_seqcount from getting corrupted.

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

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Sep 7, 2026
No patch confirmed yet.
generic

netfs: Fix potential for tearing in ->remote_i_size and ->zero_point - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55970f238d495517edc961d55c44c772594d0969
generic

netfs: Fix potential for tearing in ->remote_i_size and ->zero_point - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c8f4742bb76117d735f92a3932d85239b16c494

Vendor Advisories for CVE-2026-64160(2)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-11ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-11ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-11ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-11ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-11ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-11ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1—

All Vendor Advisories

(6)

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 29× in last 7d / 246× 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 490 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64160?
CVE-2026-64160 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential for tearing in ->remoteisize and ->zero_point Fix potential tearing in using ->remoteisize and ->zero_point by copying isizeread() and isizewrite() and using the same seqcount as for i_size. We need to make…
When was CVE-2026-64160 disclosed?
CVE-2026-64160 was first published in the National Vulnerability Database on July 19, 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-64160 actively exploited?
CVE-2026-64160 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64160?
CVE-2026-64160 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64160?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64160, 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-64160

Explore →

Is Your Infrastructure Affected by CVE-2026-64160?

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

Start Free Scan →Browse All CVEs