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_set
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-53397 is a memory leak vulnerability in the Linux kernel's NFS server (nfsd) implementation that occurs during the decoding of SETACL requests. When nfsaclsvc_decode_setaclargs() or nfs3svc_decode_setaclargs() processes ACL data, it makes two separate calls to nfs_stream_decode_acl()—one for NFS_ACL and one for NFS_DFACL. If the first call succeeds and allocates a posix_acl structure, but the second call fails, the decoder returns false without properly freeing the first allocation, leaving a dangling pointer in argp->acl_access. This vulnerability affects Linux systems running NFS server functionality, particularly those exposed to network-accessible NFS services. While the CVSS score of 7.5 indicates high severity, the practical impact depends on attack surface exposure and the frequency with which an attacker can trigger decode failures.
Casky's extended reasoning capabilities would detect the attack patterns behind this vulnerability by analyzing memory management flows and resource allocation chains in kernel code. Practitioners using Casky would identify this through detection of anomalous resource exhaustion patterns—specifically, repeated NFS SETACL requests that trigger decode failures, progressively consuming kernel memory without corresponding cleanup. The security skills mapped to MITRE ATT&CK would correlate this with T1499 (Endpoint Denial of Service) patterns, as an attacker could exploit this leak to exhaust available kernel memory and degrade or crash the NFS service. A practitioner's findings would highlight suspicious sequences of malformed SETACL protocol messages from specific source IPs, coupled with system memory growth that correlates with NFS service activity, indicating potential exploitation attempts.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-53397. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation