CVE-2026-99310

nfsd: hold cl_lock in client_has_openowners()

Published Nov 16, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

nfsd: hold cl_lock in client_has_openowners()

client_has_openowners() walks clp->cl_openowners and reads so_stateids
without clp->cl_lock. nfs4_put_stateowner() unhashes that openowner under
cl_lock and then frees it, so a concurrent EXCHANGE_ID with mismatched
creds can use-after-free the nfs4_openowner.

BUG: KASAN: slab-use-after-free in client_has_state+0x10a/0x140
fs/nfsd/nfs4state.c:3718 client_has_openowners()
nfsd4_exchange_id
nfsd4_proc_compound
nfsd_dispatch
svc_process

Take clp->cl_lock while client_has_openowners() walks the openowner
list.

Analysis

AI-generated

Technical impact

The Linux kernel contains a race condition in the NFSv4 state management code that allows an attacker to trigger a use‑after‑free by sending a malicious nfs4_exchange_id request with mismatched credentials. This flaw corrupts the memory used for openowner objects and may enable arbitrary code execution on the NFS server, compromising confidentiality, integrity, and availability.

Affected Systems

The vulnerability affects the Linux kernel in any release that implements the buggy NFSv4 c_openowners logic. No specific version range is listed, so any system running an unpatched kernel may be vulnerable.

Risk and Exploitability

The advisory does not provide a CVSS score or EPSS data, but the use‑after‑free nature of the flaw is considered high severity. A remote attacker who can send crafted NFS requests to the vulnerable server could trigger the memory corruption. While the flaw is not listed in the CISA KEV catalog and no public exploit is known, its severity warrants urgent attention.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the commit that locks clp->cl_lock while traversing the openowner list
  • If an immediate kernel upgrade is not possible, restrict NFS traffic to trusted hosts or disable NFSv4 on the affected servers
  • Reboot the system after the patch to ensure the kernel image in use contains the fix

Generated by OpenCVE AI on November 16, 2026 at 11:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-362
CWE-416
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: nfsd: hold cl_lock in client_has_openowners() client_has_openowners() walks clp->cl_openowners and reads so_stateids without clp->cl_lock. nfs4_put_stateowner() unhashes that openowner under cl_lock and then frees it, so a concurrent EXCHANGE_ID with mismatched creds can use-after-free the nfs4_openowner. BUG: KASAN: slab-use-after-free in client_has_state+0x10a/0x140 fs/nfsd/nfs4state.c:3718 client_has_openowners() nfsd4_exchange_id nfsd4_proc_compound nfsd_dispatch svc_process Take clp->cl_lock while client_has_openowners() walks the openowner list.
Title nfsd: hold cl_lock in client_has_openowners()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

  • CWE-416

    Use After Free

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 16, 2026, 9:59 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Nov 16, 2026, 10:17 AM
Modified
Nov 16, 2026, 10:17 AM