UBUNTU-CVE-2026-99310: Use After Free
In the Linux kernel, the following vulnerability has been resolved: nfsd: hold cllock in clienthasopenowners() clienthasopenowners() walks clp->clopenowners and reads sostateids without clp->cllock. nfs4putstateowner() unhashes that openowner under cllock and then frees it, so a concurrent EXCHANGEID with mismatched creds can use-after-free the nfs4openowner. BUG: KASAN: slab-use-after-free in clienthasstate+0x10a/0x140 fs/nfsd/nfs4state.c:3718 clienthasopenowners() nfsd4exchangeid nfsd4proccompound nfsddispatch svcprocess Take clp->cllock while clienthasopenowners() walks the openowner list.
Affected Software
Event History
Frequently Asked Questions
What conditions are required to trigger this issue?
The race occurs in the NFS server's state handling when client_has_openowners() walks a client's open-owner list concurrently with nfs4_put_stateowner() removing and freeing an open owner. The reported path involves an EXCHANGE_ID request with mismatched credentials.
Which systems are in scope?
The affected software list includes Ubuntu linux, linux-fips, linux-aws, linux-azure, linux-gcp, linux-oracle, linux-aws-fips, and linux-azure-fips packages. The provided data does not identify specific affected or fixed package versions.
What is the likely impact of successful exploitation?
The flaw is a use-after-free of an nfs4_openowner object in NFS server code. The supplied report shows KASAN detecting a slab use-after-free during client state checking; it does not state a confirmed impact beyond that memory-safety failure.
How can I identify this issue in diagnostics?
A relevant diagnostic signature is a KASAN slab-use-after-free report in client_has_state, with the stack including client_has_openowners(), nfsd4_exchange_id(), nfsd4_proc_compound(), nfsd_dispatch(), and svc_process().