CVE-2026-64058

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:

netfs: Fix netfs_read_folio() to wait on writeback

Fix netfs_read_folio() to wait for an ongoing writeback to complete so that it can trust the dirty flag and whatever is attached to folio->private (folio->private may get cleaned up by the collector before it clears the writeback flag).

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 19, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

netfs: Fix netfs_read_folio() to wait on writeback - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfs: Fix netfs_read_folio() to wait on writeback - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfs: Fix netfs_read_folio() to wait on writeback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b8271cccdd5e43cc8d738afb8b51f6ad05b1cb4b

Vendor Advisories for CVE-2026-64058(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)

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

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.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
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)

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 28× in last 7d / 157× 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 203 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64058?
CVE-2026-64058 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: netfs: Fix netfsreadfolio() to wait on writeback Fix netfsreadfolio() to wait for an ongoing writeback to complete so that it can trust the dirty flag and whatever is attached to folio->private (folio->private may get cleaned up by…
When was CVE-2026-64058 disclosed?
CVE-2026-64058 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-64058 actively exploited?
CVE-2026-64058 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64058?
CVE-2026-64058 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64058?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64058, 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-64058

Explore →

Is Your Infrastructure Affected by CVE-2026-64058?

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

Start Free Scan →Browse All CVEs