CVE-2026-53397

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: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

nfsd: fix posix_acl leak on SETACL decode failure

nfsaclsvc_decode_setaclargs() and nfs3svc_decode_setaclargs() each call nfs_stream_decode_acl() twice, first for NFS_ACL and then for NFS_DFACL. Each successful call transfers ownership of a freshly allocated posix_acl into argp->acl_access or argp->acl_default. If the first call succeeds but the second fails, the decoder returns false and argp->acl_access is left dangling.

ACLPROC2_SETACL.pc_release was wired to nfssvc_release_attrstat and ACLPROC3_SETACL.pc_release was wired to nfs3svc_release_fhandle. Both only call fh_put() and have no knowledge of the ACL fields on argp. The posix_acl_release() pairs sat at the out: labels inside nfsacld_proc_setacl() and nfsd3_proc_setacl(), but svc_process() skips pc_func when pc_decode returns false, so that cleanup is unreachable on decode failure:

svc_process_common() pc_decode() /* decode_setaclargs: false */ /* pc_func skipped */ pc_release() /* fh_put only -- ACLs leaked */

The orphaned posix_acl is leaked for the lifetime of the server.

Fix by adding nfsaclsvc_release_setacl() and nfs3svc_release_setacl(), which release both argp->acl_access and argp->acl_default in addition to fh_put(), and wiring them as pc_release for their respective SETACL procedures. pc_release runs on every path svc_process() takes after decode, including decode failure, so the posix_acl_release() pairs are removed from the proc functions' out: labels to keep ownership in one place. This matches the existing release_getacl() pattern used by the sibling GETACL procedures.

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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

nfsd: fix posix_acl leak on SETACL decode failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfsd: fix posix_acl leak on SETACL decode failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfsd: fix posix_acl leak on SETACL decode failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfsd: fix posix_acl leak on SETACL decode failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfsd: fix posix_acl leak on SETACL decode failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/887f92ceccf3eacd5f2402db21254d66372fae00
generic

nfsd: fix posix_acl leak on SETACL decode failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e96239fddcefacf6afe6c498357be68eacbcabc
generic

nfsd: fix posix_acl leak on SETACL decode failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/136b416593f1349cf6f72c8e3d18f0f204ee8545
generic

nfsd: fix posix_acl leak on SETACL decode failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0853ac544c590880d797b04daa33fcb72b6be0e1

Vendor Advisories for CVE-2026-53397(6)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
redhatkernel-0:5.14.0-687.44.1.el9_82026-09-04redhat
redhatkernel-rt-0:4.18.0-553.159.1.rt7.500.el8_102026-09-03redhat
redhatkernel-0:4.18.0-553.159.1.el8_102026-09-03redhat
redhatkernel-0:6.12.0-211.50.1.el10_22026-09-01redhat

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

(5 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.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
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.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53397?
CVE-2026-53397 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: nfsd: fix posix_acl leak on SETACL decode failure nfsaclsvcdecodesetaclargs() and nfs3svcdecodesetaclargs() each call nfsstreamdecodeacl() twice, first for NFSACL and then for NFS_DFACL. Each successful call transfers ownership of…
When was CVE-2026-53397 disclosed?
CVE-2026-53397 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-53397 actively exploited?
CVE-2026-53397 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53397?
CVE-2026-53397 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-53397?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53397, 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-53397

Explore →

Is Your Infrastructure Affected by CVE-2026-53397?

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

Start Free Scan →Browse All CVEs