Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2025-38724

A use-after-free vulnerability exists in the Linux kernel's NFS server implementation. The nfsd4_setclientid_confirm() function fails to check the return value from get_client_locked(), allowing a race condition where a confirmed client can expire and later be accessed after being freed. This flaw can be exploited to execute arbitrary code with high impact, as reflected by a CVSS v3.1 base score of 9.8 (Critical).

publishedSep 4, 2025
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
6th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 29, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel users, including systems running Debian Linux 11.0.

02

Real-world impact

An attacker could trigger the race condition to cause a use-after-free, potentially leading to privilege escalation, denial of service, or arbitrary code execution.

03

Why this severity

The CVSS score of 9.8 reflects a network‑exploitable flaw with low attack complexity, no privileges or user interaction required, and high impacts to confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 01Obtain the latest Linux kernel update from your distribution that includes the fix for CVE-2025-38724 (as indicated in the NVD description).
  2. 02Install or upgrade the kernel package.
  3. 03Reboot the system to load the patched kernel.

NVD description (indicates the vulnerability has been resolved in the Linux kernel).

05

Timeline

  1. Sep 4, 2025 · Sep 4, 2025
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 30, 2026 · 6h ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 30, 2026 · 2h ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

NVD advisory ↗Search advisories ↗
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →