CVE Intelligence
High Memory corruption

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

Published Sep 4, 2025 · Updated Oct 19, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+5
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.39%
ahead of 32% of scored CVEs · Oct 19, 2026
Affects
Debian
Debian Linux and 2 more
CVSS base
7.8
High · 4 source(s)
Prioritization reference: 9.8 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Linux Linux, Linux Linux Kernel).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Debian Debian Linux version 11.0 Vulnerable NIST National Vulnerability Database
Linux Linux ≥ d20c11d86d8f821a64eac7d6c8f296f06d935f4f and < 3f252a73e81aa01660cb426735eab932e6182e8dversion 3.17≥ d20c11d86d8f821a64eac7d6c8f296f06d935f4f and < 908e4ead7f757504d8b345452730636e298cbf68≥ d20c11d86d8f821a64eac7d6c8f296f06d935f4f and < 571a5e46c71490285d2d8c06f6b5a7cbf6c7edd1≥ d20c11d86d8f821a64eac7d6c8f296f06d935f4f and < 36e83eda90e0e4ac52f259f775b40b2841f8a0a3≥ d20c11d86d8f821a64eac7d6c8f296f06d935f4f and < 74ad36ed60df561a303a19ecef400c7096b20306≥ d20c11d86d8f821a64eac7d6c8f296f06d935f4f and < d71abd1ae4e0413707cd42b10c24a11d1aa71772≥ d20c11d86d8f821a64eac7d6c8f296f06d935f4f and < 22f45cedf281e6171817c8a3432c44d788c550e1
and 2 more ≥ d20c11d86d8f821a64eac7d6c8f296f06d935f4f and < f3aac6cf390d8b80e1d82975faf4ac61175519c0≥ d20c11d86d8f821a64eac7d6c8f296f06d935f4f and < d35ac850410966010e92f401f4e21868a9ea4d8b
Vulnerable CVE Program (cve.org) e CISA ADP
Linux Linux Kernel ≥ 6.16 and < 6.16.2≥ 6.13 and < 6.15.11≥ 6.7 and < 6.12.43≥ 6.2 and < 6.6.103≥ 5.16 and < 6.1.149≥ 5.11 and < 5.15.190≥ 5.5 and < 5.10.241≥ 3.17 and < 5.4.297 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — Linux via CVE Program (cve.org) e CISA ADP
7.8 CVSS 3.1 High 1.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.8 (416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-416 · Use After Free

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 19, 2026 · NIST National Vulnerability Database
  • Affected products added · linux/linux kernel, debian/debian linux
    Oct 19, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8 → 7.8
    Oct 19, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Modified
    Oct 19, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 19, 2026
  • Affected products added · linux/linux
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 9.8
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 19, 2026 · Alertas do Telegram
  • 2025
  • CVE published
    Sep 4, 2025 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 19, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 19, 2026 – Oct 19, 2026

References

15 on the record

Elsewhere on this site

Debian
every CVE for this vendor
Memory corruption
same class
CWE-416
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
  • CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
  • CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
  • CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 1d
  • CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 1d
  • CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-38724 is "nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()", rated High. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.39% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.