CVE-2026-53026

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 7.5; sources differ by 0.0.

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

A fix is available — apply it.

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

NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg

In nfsd4_add_rdaccess_to_wrdeleg, if fp->fi_fds[O_RDONLY] is already set by another thread, __nfs4_file_get_access should not be called to increment the nfs4_file access count since that was already done by the thread that added READ access to the file. The extra fi_access count in nfs4_file can prevent the corresponding nfsd_file from being freed.

When stopping nfs-server service, these extra access counts trigger a BUG in kmem_cache_destroy() that shows nfsd_file object remaining on __kmem_cache_shutdown.

This problem can be reproduced by running the Git project's test suite over NFS.

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

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4584229395d0d65bd517780afe97ffea07cb2c3d

Vendor Advisories for CVE-2026-53026(2)

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

Patch Availability(10)

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 (140 versions)7.0.10-1

Additional Vendor Advisories

(9)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-53026?
CVE-2026-53026 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: NFSD: fix nfs4file access extra count in nfsd4addrdaccessto_wrdeleg In nfsd4addrdaccesstowrdeleg, if fp->fifds[ORDONLY] is already set by another thread, nfs4fileget_access should not be called to increment the nfs4_file access…
When was CVE-2026-53026 disclosed?
CVE-2026-53026 was first published in the National Vulnerability Database on June 24, 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-53026 actively exploited?
CVE-2026-53026 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-53026?
CVE-2026-53026 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53026?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53026, 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-53026

Explore →

Is Your Infrastructure Affected by CVE-2026-53026?

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