CVE-2026-53395

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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 dead ACL conflict guard in nfsd4_create

nfsd4_create() steals create->cr_dpacl/cr_pacl into the local nfsd_attrs via the designated initializer, then immediately sets the source pointers to NULL. The subsequent conflict guard tests the already-nilled source fields, making it permanently dead code:

if (create->cr_acl) { if (create->cr_dpacl || create->cr_pacl) /* always false */

When a client encodes both FATTR4_WORD0_ACL and FATTR4_WORD2_POSIX_{DEFAULT,ACCESS}_ACL in the same CREATE fattr bitmap, nfsd4_acl_to_attr() overwrites attrs.na_pacl/na_dpacl without releasing the originals, leaking two posix_acl slab objects per request. Repeated requests cause unbounded slab exhaustion.

Fix by checking attrs.na_dpacl/na_pacl (the stolen values) instead of the nilled create->cr_dpacl/cr_pacl, matching the correct pattern already used in nfsd4_setattr().

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

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (2)

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

nfsd: fix dead ACL conflict guard in nfsd4_create - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfsd: fix dead ACL conflict guard in nfsd4_create - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8371cc5c0a2cc2a71b3dcfd47ff1f7fcfc526a5e

Vendor Advisories for CVE-2026-53395(1)

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

Patch Availability(4)

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.1~rc7-1~exp1 (156 versions)7.1.3-1

Weakness Classification(1)

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

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 18× in last 7d / 74× 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 190 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53395?
CVE-2026-53395 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: nfsd: fix dead ACL conflict guard in nfsd4_create nfsd4create() steals create->crdpacl/cr_pacl into the local nfsd_attrs via the designated initializer, then immediately sets the source pointers to NULL. The subsequent conflict…
When was CVE-2026-53395 disclosed?
CVE-2026-53395 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-53395 actively exploited?
CVE-2026-53395 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 58.9% of all scored CVEs.
What is the CVSS score of CVE-2026-53395?
CVE-2026-53395 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-53395?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53395, 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-53395

Explore →

Is Your Infrastructure Affected by CVE-2026-53395?

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