Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-53397nfsd: fix posix_acl leak on SETACL decode failure

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 40 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53397, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.53% · top 55% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected a257cdd0e2179630d3201c32ba14d7fcb3c3a055 – < b2eb1ffd511d1b3c3e21122f97cbbccea411e277
    • affected a257cdd0e2179630d3201c32ba14d7fcb3c3a055 – < b94c4be77682aab06d65ca7296149e3bcfb37353
    • affected a257cdd0e2179630d3201c32ba14d7fcb3c3a055 – < 887f92ceccf3eacd5f2402db21254d66372fae00
    • affected a257cdd0e2179630d3201c32ba14d7fcb3c3a055 – < 1e96239fddcefacf6afe6c498357be68eacbcabc
    • affected a257cdd0e2179630d3201c32ba14d7fcb3c3a055 – < bd69a825485168ef74e815ecb286754b570fdcc7
    • affected a257cdd0e2179630d3201c32ba14d7fcb3c3a055 – < 136b416593f1349cf6f72c8e3d18f0f204ee8545
    • affected a257cdd0e2179630d3201c32ba14d7fcb3c3a055 – < a5b42c1e4ff2befaa6b96f7cbf32174751eba083
    • affected a257cdd0e2179630d3201c32ba14d7fcb3c3a055 – < 0853ac544c590880d797b04daa33fcb72b6be0e1
  • Linux · Linux

    • affected 2.6.13
    • unaffected < 2.6.13
    • unaffected 5.10.260 – ≤ 5.10.*
    • unaffected 5.15.211 – ≤ 5.15.*
    • unaffected 6.1.177 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.38 – ≤ 6.18.*
    • unaffected 7.1.3 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53397 badge
[![CVE-2026-53397](https://cveledger.app/badge/CVE-2026-53397.svg)](https://cveledger.app/cve/CVE-2026-53397)

Record last updated .