CVE-2026-53396

published 19 Jul 2026 · updated 17 Aug 2026

nfsd: fix posix_acl leak and ignored error in nfsd4_create_file

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 18cf006a08babec0bbac2a3784f8f28e56e47490 and Kernel 24c975bbdd564d7d0ad90294bfa69729830345de.

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix posix_acl leak and ignored error in nfsd4_create_file nfsd4_create_file() has two bugs in its ACL handling: The return value of nfsd4_acl_to_attr() is silently discarded. When the NFSv4-to-POSIX ACL conversion fails (e.g., -EINVAL for unsupported ACE types), the file is created without any ACL and the client receives NFS4_OK. This violates RFC 7530/8881 which require the server to reject unsupported attributes on CREATE. When start_creating() fails after ACL attributes have been populated in attrs (either via nfsd4_acl_to_attr or via ownership transfer from open->op_dpacl/op_pacl), the function jumps to out_write which skips nfsd_attrs_free(). The posix_acl allocations are leaked. A client can trigger this repeatedly with OPEN(CREATE), ACL attributes, and an invalid filename (e.g., longer than NAME_MAX). Fix both by capturing the nfsd4_acl_to_attr() return value and by changing the early error paths to jump to out instead of out_write. Initialize child to ERR_PTR(-EINVAL) so that end_creating() is safe to call even if start_creating() was never reached.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.19, >=7ab96df840e60eb933abfe65fc5fe44e72f16dc0 <18cf006a08babec0bbac2a3784f8f28e56e47490, >=7ab96df840e60eb933abfe65fc5fe44e72f16dc0 <24c975bbdd564d7d0ad90294bfa69729830345de18cf006a08babec0bbac2a3784f8f28e56e47490, 24c975bbdd564d7d0ad90294bfa69729830345de

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-53396 severity on Zeptric[![CVE-2026-53396](https://zeptric.io/badge/cve/CVE-2026-53396.svg)](https://zeptric.io/cve/CVE-2026-53396)