CVE-2026-64298

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

NFSv4: include MAY_WRITE in open permission mask for O_TRUNC

POSIX requires write permission to truncate a file, so an open() that specifies O_TRUNC must be authorized for write access regardless of the O_ACCMODE access mode.

nfs_open_permission_mask() builds the access mask passed to nfs_may_open(), which is the local authorization gate for OPENs the client serves itself from a cached write delegation via the can_open_delegated() path in nfs4_try_open_cached(). The mask is derived from O_ACCMODE alone, so an open(O_RDONLY | O_TRUNC) against a file the caller cannot write requests only MAY_READ and passes the local check. The OPEN is then satisfied locally and the truncation is issued to the server as a SETATTR(size=0) over the delegation stateid, which the server accepts under standard write-delegation semantics. POSIX requires that this open fail with EACCES.

Include MAY_WRITE in the mask whenever O_TRUNC is set so the local check matches the access the server would have enforced.

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

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

NFSv4: include MAY_WRITE in open permission mask for O_TRUNC - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4: include MAY_WRITE in open permission mask for O_TRUNC - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4: include MAY_WRITE in open permission mask for O_TRUNC - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4: include MAY_WRITE in open permission mask for O_TRUNC - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4: include MAY_WRITE in open permission mask for O_TRUNC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5140f099ecd8a2f2808b7f7b720ee1bad8468974
generic

NFSv4: include MAY_WRITE in open permission mask for O_TRUNC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4817c8974315b666e895b7d1bb83cd3664c323b1
generic

NFSv4: include MAY_WRITE in open permission mask for O_TRUNC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30fdf4df6c3c00efec947e4ddf97f0fdd4473628
generic

NFSv4: include MAY_WRITE in open permission mask for O_TRUNC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22c1fd1355ad4ca27aa7f0fa02719122dd92d9de

Patch Availability(9)

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

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 30× in last 7d / 127× 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 260 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64298?
CVE-2026-64298 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: NFSv4: include MAYWRITE in open permission mask for OTRUNC POSIX requires write permission to truncate a file, so an open() that specifies O_TRUNC must be authorized for write access regardless of the O_ACCMODE access mode.…
When was CVE-2026-64298 disclosed?
CVE-2026-64298 was first published in the National Vulnerability Database on July 25, 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-64298 actively exploited?
CVE-2026-64298 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 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64298?
CVE-2026-64298 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-64298?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64298, 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-64298

Explore →

Is Your Infrastructure Affected by CVE-2026-64298?

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