CVE-2026-99310 · Infrastructure
NO FIX YET
The Linux kernel's NFS server (nfsd) reads openowner state without holding the client lock, so a concurrent EXCHANGE_ID request can free memory that is still being read. The sources describe a KASAN-reported slab use-after-free; they do not state what an attacker can achieve beyond that.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Systems running the Linux kernel with the nfsd NFS server enabled are the ones exposed; hosts that do not serve NFSv4 are not. The sources do not name affected kernel versions or whether default configurations are involved.
Not affected if no-nfs-server
Who cares linux-kernel, nfs-server, nfsd
Unknown from the sources.
Unknown from the sources.
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.
NVD data is provided by NIST and is public domain · . Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.