CVE-2026-90038

NFSD: Prevent client use-after-free during export state revocation

Published Sep 16, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

NFSD: Prevent client use-after-free during export state revocation

nfsd4_revoke_export_states() has the same use-after-free as
nfsd4_revoke_states(): it drops nn->client_lock across
revoke_one_stid() and the following read of clp->cl_minorversion, but
the stateid reference it holds does not pin the client. A teardown
racing the dropped lock can free the client while revoke_one_stid()
still dereferences it.

exportfs -u drives this path through NFSD_CMD_UNLOCK_EXPORT, so an
administrator removing an export can race a client expiry.

Skip a client that is already expiring and otherwise pin it with
cl_rpc_users under client_lock before dropping the lock, matching
nfsd4_revoke_states().

Analysis

AI-generated

Technical impact

The changed code in the Linux kernel’s NFS server (NFSD) exposes a use‑after‑free flaw in the function that revokes client export states. When an export is revoked, the lock protecting the client structure is released before a reference to the client is safely held; this allows the client object to be freed while the revoke routine still dereferences it. The result is a memory corruption that an attacker could exploit to execute arbitrary code with the kernel's privileges.

Affected Systems

All versions of the Linux kernel that include NFSD, before the application of the patch that introduced the fix. The issue is present in the kernel source for the Linux distribution and is not limited to a specific vendor or distribution version.

Risk and Exploitability

This vulnerability receives a CVSS score of 9.8, indicating critical severity, but its EPSS score is under 1 %, suggesting a low probability of exploitation in current datasets. The flaw is not listed in CISA’s KEV catalog. Attacks would typically require an attacker to trigger an export revocation while clients are connected, which generally demands local or privileged administrative access. The lack of a publicly advertised exploitation vector further reduces immediate risk, but the high impact warrants prompt remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest kernel update that contains the NFSD use‑after‑free fix.
  • Restrict the use of the exportfs command to trusted administrators and ensure exports are not removed while NFS clients are active.
  • If NFSv4 is not required for your environment, consider disabling the nfsv4 service until the patch has been applied.

Generated by OpenCVE AI on September 18, 2026 at 04:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: NFSD: Prevent client use-after-free during export state revocation nfsd4_revoke_export_states() has the same use-after-free as nfsd4_revoke_states(): it drops nn->client_lock across revoke_one_stid() and the following read of clp->cl_minorversion, but the stateid reference it holds does not pin the client. A teardown racing the dropped lock can free the client while revoke_one_stid() still dereferences it. exportfs -u drives this path through NFSD_CMD_UNLOCK_EXPORT, so an administrator removing an export can race a client expiry. Skip a client that is already expiring and otherwise pin it with cl_rpc_users under client_lock before dropping the lock, matching nfsd4_revoke_states().
Title NFSD: Prevent client use-after-free during export state revocation
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

No weakness.

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 8:56 AM
Reserved
Sep 11, 2026, 7:38 PM
Status
Received
Published
Sep 16, 2026, 11:17 AM
Modified
Oct 19, 2026, 9:18 AM