CVE-2026-64069

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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 cancellation of a DIO and single read subrequests

When the preparation of a new subrequest for a read fails, if the subrequest has already been added to the stream->subrequests list, it can't simply be put and abandoned as the collector may see it. Also, if it hasn't been queued yet, it has two outstanding refs that both need to be put. Both DIO read and single-read dispatch fail at this; further, both differ in the order they do things to the way buffered read works.

Fix cancellation of both DIO-read and single-read subrequests that failed preparation by the following steps:

(1) Harmonise all three reads (buffered, dio, single) to queue the subreq before prepping it.

(2) Make all three call netfs_queue_read() to do the queuing.

(3) Set NETFS_RREQ_ALL_QUEUED independently of the queuing as we don't know the length of the subreq at this point.

(4) In all cases, set the error and NETFS_SREQ_FAILED flag on the subreq and then call netfs_read_subreq_terminated() to deal with it. This will pass responsibility off to the collector for dealing with it.

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

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 26, 2026
No patch confirmed yet.
generic

netfs: Fix cancellation of a DIO and single read subrequests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f0f7ac1915abc0d202f0eb4b003a6548a5ba60d
generic

netfs: Fix cancellation of a DIO and single read subrequests - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfs: Fix cancellation of a DIO and single read subrequests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5366199be46fb53de62861721d34ba816e7e440e

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

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

(1 across 1 ecosystem)
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)

Data Freshness Timeline

(refreshed 62× in last 7d / 368× 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 439 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64069?
CVE-2026-64069 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: netfs: Fix cancellation of a DIO and single read subrequests When the preparation of a new subrequest for a read fails, if the subrequest has already been added to the stream->subrequests list, it can't simply be put and abandoned…
When was CVE-2026-64069 disclosed?
CVE-2026-64069 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-64069 actively exploited?
CVE-2026-64069 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 63.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64069?
CVE-2026-64069 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64069?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64069, 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-64069

Explore →

Is Your Infrastructure Affected by CVE-2026-64069?

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