CVE-2026-89671

CVE CVE-2026-89671EUVD EUVD-2026-76583Published 2026-09-11T19:45:56.000ZLast changed 2026-09-14T12:01:56.000ZCVSS 9.1

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: nfsd: gate nfs3 setacl by argp->mask nfsd3_proc_setacl() calls set_posix_acl() unconditionally for both ACL_TYPE_ACCESS and ACL_TYPE_DEFAULT, passing argp->acl_access and argp->acl_default verbatim. The NFSv3 ACL decoder only populates those pointers when the corresponding mask bit is set: nfs3svc_decode_setaclargs() if (args->mask & NFS_ACL) decode into acl_access if (args->mask & NFS_DFACL) decode into acl_default /* otherwise the pointer stays NULL (pc_argzero) */ nfsd3_proc_setacl() set_posix_acl(.., ACL_TYPE_ACCESS, argp->acl_access) set_posix_acl(.., ACL_TYPE_DEFAULT, argp->acl_default) set_posix_acl(idmap, dentry, type, NULL) is the VFS "remove this ACL type" operation. A NULL pointer that means "the client did not send this arm" is therefore indistinguishable from "the client asked to remove this ACL". A SETACL with mask=NFS_ACL silently drops the directory's default ACL; mask=0 drops both. The sibling nfsd3_proc_getacl() already consults argp->mask before touching each arm; mirror that in setacl. Fix by wrapping each set_posix_acl() call in the matching mask bit check and initializing error to 0 before inode_lock so that a request with neither bit set leaves the on-disk ACLs untouched and returns nfs_ok. The out_drop_lock path and the unconditional posix_acl_release() at out: are preserved; both NULL-tolerate the skipped arms.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 6.12.109; patch: 7.3-rc1; a257cdd0e2179630d3201c32ba14d7fcb3c3a055 <ff99ed007f065198fd723152405c22aa558f700b; patch: 7.2.4; patch: 0; patch: 6.18.50; a257cdd0e2179630d3201c32ba14d7fcb3c3a055 <3be1d8611dae4829e4608007db29f4a8748c37b2; a257cdd0e2179630d3201c32ba14d7fcb3c3a055 <453d7198a0ab07a12d46e0575861ac7b932da17e; patch: 6.6.157; a257cdd0e2179630d3201c32ba14d7fcb3c3a055 <68a80b26efdff1d09f8ae1773c6a915abb9e191d; 2.6.13; a257cdd0e2179630d3201c32ba14d7fcb3c3a055 <b3bff820d068ea59767d4e91a3258231a879da5f

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.