Look up another CVE · open CVE-2026-89686 in the interactive tracker
CVE-2026-89686
nfsd: fix BUG_ON in nfsd4_alloc_layout_stateid on racing delegation revoke
Published 2026-09-11 (37 days ago) by the Linux kernel CNA. Subsystem fs/nfsd. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-89686 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 | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| 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
nfsd4_alloc_layout_stateid reads fp->fi_deleg_file without holding fi_lock when the parent stateid is a delegation. A concurrent delegation revoke via the laundromat can clear fi_deleg_file under fi_lock, causing nfsd_file_get() to return NULL and triggering the BUG_ON. This race is client-reachable: two NFS clients can trigger it by having one hold a delegation while another opens the same file to force a recall. When the first client doesn't respond to the recall, the laundromat revokes it. A concurrent LAYOUTGET from any client using the delegation stateid hits the race window. Fix this by taking fi_lock around the fi_deleg_file read in the SC_TYPE_DELEG path, matching the locking discipline of the find_any_file() arm, and replacing the BUG_ON with a graceful error return that cleans up the partially-initialized layout stateid.
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/nfs4layouts.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_PNFS' /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_PNFS
- 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.66%, higher than 50.7% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- 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 |
|---|---|---|
| 4.0 | 6.12.109 | c517f2749875 |
| 4.0 | 6.18.50 | 607a56fea772 |
| 4.0 | 7.2.4 | 97bda8b4284d |
| 4.0 | 7.3 | ca94ba361720 |
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 flaw is in nfsd pNFS LAYOUTGET (nfsd4_alloc_layout_stateid in fs/nfsd/nfs4layouts.c). A remote NFSv4.1 client reaches it over TCP/2049 via nfsd_dispatch to nfsd4_proc_compound to nfsd4_layoutget, so no local access to the NFS server is required.
- AC:LAttack complexity, low
- The attacker controls both sides of the race: one NFS client obtains a delegation while another OPENs the same file to force recall, then the first client withholds CB_RECALL and issues concurrent LAYOUTGET with the delegation stateid as the laundromat runs put_deleg_file. The sequence is retryable and can be timed using FATTR4_LEASE_TIME.
- PR:NPrivileges required, none
- Typical nfsd deployments accept AUTH_SYS/AUTH_NULL without cryptographic authentication. Any host allowed by the export ACL can EXCHANGE_ID/CREATE_SESSION, OPEN to receive a delegation, and LAYOUTGET; no local account or capability on the NFS server is required.
- UI:NUser interaction, none
- The attacking NFS clients drive the OPEN, recall, and LAYOUTGET compounds themselves against an already-running nfsd export. No victim user action such as mounting a filesystem or opening a file on the server is required.
- S:UScope, unchanged
- The unlocked fi_deleg_file load and resulting BUG_ON or nfsd_file use-after-free occur in kernel nfsd state on the NFS server host. Impact stays in that kernel security authority and does not cross a VM, IOMMU, or sandbox boundary.
- C:HConfidentiality impact, high
- put_deleg_file may drop the last nfsd_file ref and call_rcu-free it (KMEM_CACHE flags 0, not SLAB_TYPESAFE_BY_RCU) while LAYOUTGET still calls nfsd_file_get on the stale pointer. After slab reuse the layout stateid's nf_file can be leveraged for kernel information disclosure.
- I:HIntegrity impact, high
- The same stale nfsd_file pointer is used for refcount_inc_not_zero and later nfsd4_layout_setlease/kernel_setlease on nf_file. Heap reuse of the nfsd_file slab enables an arbitrary write or control-flow hijack per kernel UAF scoring guidance.
- A:HAvailability impact, high
- When nfsd_file_get returns NULL the original code hits BUG_ON(!ls->ls_file), oopsing or panicking the nfsd thread. Even without that assertion, use-after-free of nfsd_file crashes nfsd, and the attacker can repeat LAYOUTGET to deny NFS service.