CVE-2025-38724: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()
In the Linux kernel, the following vulnerability has been resolved:
nfsd: handle getclientlocked() failure in nfsd4setclientidconfirm()
Lei Lu recently reported that nfsd4setclientidconfirm() did not check the return value from getclientlocked(). a SETCLIENTIDCONFIRM could race with a confirmed client expiring and fail to get a reference. That could later lead to a UAF.
Fix this by getting a reference early in the case where there is an extant confirmed client. If that fails then treat it as if there were no confirmed client found at all.
In the case where the unconfirmed client is expiring, just fail and return the result from getclientlocked().
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38724?
CVE-2025-38724 has a medium severity rating due to its potential impact on the NFS server's stability.
How do I fix CVE-2025-38724?
To mitigate CVE-2025-38724, update your Linux kernel to the latest version where this vulnerability has been patched.
What systems are affected by CVE-2025-38724?
CVE-2025-38724 affects various versions of the Linux kernel that implement NFS services.
Is CVE-2025-38724 remotely exploitable?
CVE-2025-38724 is considered potentially exploitable remotely, depending on the NFS configuration.
Who reported CVE-2025-38724?
CVE-2025-38724 was reported by researcher Lei Lu.