Linux · Linux · published 2026-11-16

CVE-2026-99310nfsd: hold cl_lock in client_has_openowners()

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-99310 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 29% of all CVEs. This Linux vulnerability: CVSS 9.8 (v3.1). Routine: patch when convenient.

Share this

Remediation#

No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (29th pct)FIRST EPSS v2026.06.15
CVSS base score9.8 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitation—CISA Vulnrichment
SSVC automatable—CISA Vulnrichment
SSVC technical impact—CISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →