CVE-2026-64062

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

netfs: Fix potential deadlock in write-through mode

Fix netfs_advance_writethrough() to always unlock the supplied folio and to mark it dirty if it isn't yet written to the end. Unfortunately, it can't be marked for writeback until the folio is done with as that may cause a deadlock against mmapped reads and writes.

Even though it has been marked dirty, premature writeback can't occur as the caller is holding both inode->i_rwsem (which will prevent concurrent truncation, fallocation, DIO and other writes) and ictx->wb_lock (which will cause flushing to wait and writeback to skip or wait).

Note that this may be easier to deal with once the queuing of folios is split from the generation of subrequests.

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

Published

July 19, 2026

Last Modified

September 2, 2026

Advisory Details (4)

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

netfs: Fix potential deadlock in write-through mode - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfs: Fix potential deadlock in write-through mode - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfs: Fix potential deadlock in write-through mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1468f39243ccb155b6d97f9a9932f610d1205d75
generic

netfs: Fix potential deadlock in write-through mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/003aa0dd26c964025acd6d1213bcdbd674db2ca9

Vendor Advisories for CVE-2026-64062(1)

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

Patch Availability(6)

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 (141 versions)7.0.12-1

Weakness Classification(1)

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

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 11× in last 7d / 52× 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 112 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64062?
CVE-2026-64062 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential deadlock in write-through mode Fix netfsadvancewritethrough() to always unlock the supplied folio and to mark it dirty if it isn't yet written to the end. Unfortunately, it can't be marked for writeback until…
When was CVE-2026-64062 disclosed?
CVE-2026-64062 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64062 actively exploited?
CVE-2026-64062 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 99.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64062?
CVE-2026-64062 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64062?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64062, 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-64062

Explore →

Is Your Infrastructure Affected by CVE-2026-64062?

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