Look up another CVE · open CVE-2026-89658 in the interactive tracker
CVE-2026-89658
NFSD: Prevent client use-after-free during NFSv4.0 revoked-state cleanup
Published 2026-09-11 (37 days ago) by the Linux kernel CNA. Subsystem fs/nfsd. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-89658 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
nfs40_clean_admin_revoked() takes a stateid reference under clp->cl_lock, drops nn->client_lock, and calls nfsd4_drop_revoked_stid(), which dereferences the stateid's client through s->sc_client->cl_lock. The stateid reference does not pin the client, so a teardown racing the dropped lock can free the client while nfsd4_drop_revoked_stid() is still using it. This cleanup runs from the laundromat, so a periodic sweep can race force_expire_client() driven by a write to the clients/<id>/ctl file. 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().
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
fs/nfsd/nfs4state.c
- What this is
- KERNEL NFSD, SUNRPC, AND LOCKD SERVERSMAINTAINERS section matched on fs/nfsd/ · linux-nfs@vger.kernel.org · Supported
- Kernel module
- nfsd
Check it on the machine
grep -wE 'CONFIG_NFSD|CONFIG_NFSD_V4' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w nfsdPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this as a loadable module. Every release below compiles it as a module on every flavour, so whether the code is in the running kernel depends on whether that module is loaded.
- bookworm, trixie, forky, sid, bookworm · linux-6.12m
- m
- a loadable module on every flavour - check lsmod, can be blacklisted
- Build switches
- CONFIG_NFSD, CONFIG_NFSD_V4
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-11 (37 days ago)source
- CVSS
- 9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.62%, higher than 48.5% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- fs/nfsd
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.9 | 6.12.109 | 0ae0d2b5c5a1 |
| 6.9 | 6.18.50 | b413ec5b23e3 |
| 6.9 | 7.2.4 | 81cf7f141386 |
| 6.9 | 7.3 | 7b4f8a1586c4 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:NAttack vector, network
- The UAF is in nfsd NFSv4.0 revoked-state cleanup (nfs40_clean_admin_revoked). A remote peer reaches it over TCP/2049 via nfsd_dispatch to nfsd4_proc_compound: SETCLIENTID/SETCLIENTID_CONFIRM (ALLOWED_WITHOUT_FH) call expire_client() while the laundromat still uses the client.
- AC:LAttack complexity, low
- The attacker controls the expire side by retrying SETCLIENTID_CONFIRM around the known lease interval, or by inducing the documented clients/<id>/ctl expire of a misbehaving client. Cleanup drops client_lock without pinning cl_rpc_users, so mark_client_expired_locked succeeds; this is not a race outside attacker influence.
- PR:NPrivileges required, none
- OP_SETCLIENTID and OP_SETCLIENTID_CONFIRM are ALLOWED_WITHOUT_FH/ALLOWED_ON_ABSENT_FS with no export check. Typical nfsd AUTH_SYS/AUTH_NULL deployments never verify RPC credentials, so any host that can reach TCP/2049 can create NFSv4.0 state and trigger the expire.
- UI:NUser interaction, none
- The attacker drives the NFS compounds that establish state and expire the client. Administrative revoke or ctl expire is a server operational condition (unexport or response to a misbehaving client), not a required victim user action.
- S:UScope, unchanged
- The freed object is struct nfs4_client in the NFS server kernel. Impact remains in that kernel security authority; there is no VM, IOMMU, or sandbox boundary crossing.
- C:HConfidentiality impact, high
- nfsd4_drop_revoked_stid() and nfs4_put_stid() dereference s->sc_client after expire_client() frees the nfs4_client. Reclaim of that slab lets an attacker groom contents and disclose kernel memory. Per kernel guidance a UAF is C:H.
- I:HIntegrity impact, high
- nfs4_put_stid() lock-and-idr_remove on the freed client's cl_lock/cl_stateids, concurrent with __destroy_client() list walks, is a slab UAF write primitive usable for heap corruption and control-flow hijacking. Per kernel guidance a UAF is I:H.
- A:HAvailability impact, high
- Use of the freed nfs4_client spinlock, IDR, and lists oopses or panics the nfsd host, fully denying service of the NFS server.