1. Home
  2. Vulnerabilities
  3. CVE-2025-38724
0.0
NA
CVE-2025-38724
nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()
Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() Lei Lu recently reported that nfsd4_setclientid_confirm() did not check the return value from get_client_locked(). a SETCLIENTID_CONFIRM 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 get_client_locked().

INFO

Published Date :

Sept. 4, 2025, 4:15 p.m.

Last Modified :

Sept. 4, 2025, 4:15 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2025-38724 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Patch the Linux kernel to properly handle client locking failures in nfsd.
  • Apply the vendor-provided patch for the nfsd vulnerability.
  • Ensure the Linux kernel is updated.
  • Recompile the kernel if necessary.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2025-38724.

URL Resource
https://git.kernel.org/stable/c/22f45cedf281e6171817c8a3432c44d788c550e1
https://git.kernel.org/stable/c/36e83eda90e0e4ac52f259f775b40b2841f8a0a3
https://git.kernel.org/stable/c/3f252a73e81aa01660cb426735eab932e6182e8d
https://git.kernel.org/stable/c/571a5e46c71490285d2d8c06f6b5a7cbf6c7edd1
https://git.kernel.org/stable/c/74ad36ed60df561a303a19ecef400c7096b20306
https://git.kernel.org/stable/c/908e4ead7f757504d8b345452730636e298cbf68
https://git.kernel.org/stable/c/d35ac850410966010e92f401f4e21868a9ea4d8b
https://git.kernel.org/stable/c/d71abd1ae4e0413707cd42b10c24a11d1aa71772
https://git.kernel.org/stable/c/f3aac6cf390d8b80e1d82975faf4ac61175519c0
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-38724 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-38724 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-38724 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2025-38724 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Sep. 04, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() Lei Lu recently reported that nfsd4_setclientid_confirm() did not check the return value from get_client_locked(). a SETCLIENTID_CONFIRM 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 get_client_locked().
    Added Reference https://git.kernel.org/stable/c/22f45cedf281e6171817c8a3432c44d788c550e1
    Added Reference https://git.kernel.org/stable/c/36e83eda90e0e4ac52f259f775b40b2841f8a0a3
    Added Reference https://git.kernel.org/stable/c/3f252a73e81aa01660cb426735eab932e6182e8d
    Added Reference https://git.kernel.org/stable/c/571a5e46c71490285d2d8c06f6b5a7cbf6c7edd1
    Added Reference https://git.kernel.org/stable/c/74ad36ed60df561a303a19ecef400c7096b20306
    Added Reference https://git.kernel.org/stable/c/908e4ead7f757504d8b345452730636e298cbf68
    Added Reference https://git.kernel.org/stable/c/d35ac850410966010e92f401f4e21868a9ea4d8b
    Added Reference https://git.kernel.org/stable/c/d71abd1ae4e0413707cd42b10c24a11d1aa71772
    Added Reference https://git.kernel.org/stable/c/f3aac6cf390d8b80e1d82975faf4ac61175519c0
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.