CVE-2026-64158

✕ Withdrawn — historical dataHIGHPre-NVD 7.3
7.3CVSS
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.3Exploit: None knownExposed: 0

A fix is available — apply it.

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

netfs: Fix write streaming disablement if fd open O_RDWR

In netfs_perform_write(), "write streaming" (the caching of dirty data in dirty but !uptodate folios) is performed to avoid the need to read data that is just going to get immediately overwritten. However, this is/will be disabled in three circumstances: if the fd is open O_RDWR, if fscache is in use (as we need to round out the blocks for DIO) or if content encryption is enabled (again for rounding out purposes).

The idea behind disabling it if the fd is open O_RDWR is that we'd need to flush the write-streaming page before we could read the data, particularly through mmap. But netfs now fills in the gaps if ->read_folio() is called on the page, so that is unnecessary. Further, this doesn't actually work if a separate fd is open for reading.

Fix this by removing the check for O_RDWR, thereby allowing streaming writes even when we might read.

This caused a number of problems with the generic/522 xfstest, but those are now fixed.

CVSS v3
7.3
EchelonGraph score
Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (4)

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

netfs: Fix write streaming disablement if fd open O_RDWR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9adf8e47d73d5e3c2fe77dea649dcde350ccd65c
generic

netfs: Fix write streaming disablement if fd open O_RDWR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7a9fa5b020a3a40f8291a71cd44c08d931da430d
generic

netfs: Fix write streaming disablement if fd open O_RDWR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70a7b9193bbbfceaab5974de66834c64ccc875dd
generic

netfs: Fix write streaming disablement if fd open O_RDWR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/616578e40dcba3f94810d841c5a52b7e3bc8ede7

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

(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

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 4× in last 7d / 106× 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 152 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64158?
CVE-2026-64158 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: netfs: Fix write streaming disablement if fd open O_RDWR In netfsperformwrite(), "write streaming" (the caching of dirty data in dirty but !uptodate folios) is performed to avoid the need to read data that is just going to get…
When was CVE-2026-64158 disclosed?
CVE-2026-64158 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-64158 actively exploited?
CVE-2026-64158 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64158?
CVE-2026-64158 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-64158?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64158, 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-64158

Explore →

Is Your Infrastructure Affected by CVE-2026-64158?

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