CVE-2025-38724CWE-416

CVE-2025-38724

Critical · published September 4, 2025

CVSS v3.1
9.8
EPSS
0%
Percentile
31.9
In the wild
Unconfirmed
What it is

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().

The record
Technical detail
CVSS v3.1
9.8 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00390 · 31.9th percentile
Weakness
CWE-416 · Use After Free
Published
2025-09-04T20:15Z
Affected products (9)
ProductVersionsFixed in
linux/linux_kernel≥ 3.17, < 5.4.2975.4.297
linux/linux_kernel≥ 5.5, < 5.10.2415.10.241
linux/linux_kernel≥ 5.11, < 5.15.1905.15.190
linux/linux_kernel≥ 5.16, < 6.1.1496.1.149
linux/linux_kernel≥ 6.2, < 6.6.1036.6.103
linux/linux_kernel≥ 6.7, < 6.12.436.12.43
linux/linux_kernel≥ 6.13, < 6.15.116.15.11
linux/linux_kernel≥ 6.16, < 6.16.26.16.2
debian/debian_linuxall versions—
References (13)
EPSS history
Timeline
  • 04 SEP 15:33Z
    nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()
    cvelistv5