CVE-2025-68803

HIGHCVSS 8/10EPSS 0.18%

Last modified

CVE-2025-68803 is a high-severity vulnerability rated 8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: NFSD: NFSv4 file creation neglects setting ACL An NFSv4 client that sets an ACL with a named principal during file creation retrieves the ACL afterwards, and finds that it is only a default ACL (based on the mode bits) and not the ACL that was requested during file creation. This violates RFC 8881 section 6.4.1.3: "the ACL attribute is set as given". The issue occurs in nfsd_create_setattr(), which calls nfsd_attrs_valid() to determine whether to call nfsd_setattr(). However, nfsd_attrs_valid() checks only for iattr changes and security labels, but not POSIX ACLs. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: NFSD: NFSv4 file creation neglects setting ACL An NFSv4 client that sets an ACL with a named principal during file creation retrieves the ACL afterwards, and finds that it is only a default ACL (based on the mode bits) and not the ACL that was requested during file creation. This violates RFC 8881 section 6.4.1.3: "the ACL attribute is set as given". The issue occurs in nfsd_create_setattr(), which calls nfsd_attrs_valid() to determine whether to call nfsd_setattr(). However, nfsd_attrs_valid() checks only for iattr changes and security labels, but not POSIX ACLs. When only an ACL is present, the function returns false, nfsd_setattr() is skipped, and the POSIX ACL is never applied to the inode. Subsequently, when the client retrieves the ACL, the server finds no POSIX ACL on the inode and returns one generated from the file's mode bits rather than returning the originally-specified ACL.

Metrics

CVSS 3.1
8/10

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS Probability
0.18%

7.5th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= c5409ce523af40d5c3019717bc5b4f72038d48be, < c182e1e0b7640f6bcc0c5ca8d473f7c57199ea3d; >= d52acd23a327cada5fb597591267cfc09f08bb1d, < 75f91534f9acdfef77f8fa094313b7806f801725; >= c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b, < 60dbdef2ebc2317266a385e4debdb1bb0e57afe1; >= c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b, < 381261f24f4e4b41521c0e5ef5cc0b9a786a9862; >= c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b, < bf4e671c651534a307ab2fabba4926116beef8c3; >= c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b, < 214b396480061cbc8b16f2c518b2add7fbfa5192; >= c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b, < 913f7cf77bf14c13cfea70e89bcb6d0b22239562; >= 5.10.220, < 5.10.248; >= 5.15.154, < 5.15.198
LinuxLinux6.0

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-68803?
In the Linux kernel, the following vulnerability has been resolved: NFSD: NFSv4 file creation neglects setting ACL An NFSv4 client that sets an ACL with a named principal during file creation retrieves the ACL afterwards, and finds that it is only a default ACL (based on the mode bits) and not the ACL that was requested during file creation. This violates RFC 8881 section 6.4.1.3: "the ACL attribute is set as given". The issue occurs in nfsd_create_setattr(), which calls nfsd_attrs_valid() to determine whether to call nfsd_setattr(). However, nfsd_attrs_valid() checks only for iattr changes and security labels, but not POSIX ACLs. When only an ACL is present, the function returns false, nfsd_setattr() is skipped, and the POSIX ACL is never applied to the inode. Subsequently, when the client retrieves the ACL, the server finds no POSIX ACL on the inode and returns one generated from the file's mode bits rather than returning the originally-specified ACL.
How severe is CVE-2025-68803?
CVE-2025-68803 has a CVSS score of 8/10 (HIGH severity). The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2025-68803?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

Are you affected by CVE-2025-68803?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST