Look up another CVE · open CVE-2026-93221 in the interactive tracker
CVE-2026-93221
nfsd: convert nfsd_net boolean flags to unsigned long flags word
Published 2026-09-24 (24 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-93221 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 | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| 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. |
The vulnerability
What the bug is
nfsd_net contains several boolean fields that are accessed from concurrent contexts without serialization. In particular, nfsd4_end_grace() guards its drain path with a plain bool: if (nn->grace_ended) return; nn->grace_ended = true; The read and the write are independent, and nothing in struct nfsd_net serializes them. At least two contexts can reach this code with no lock held: laundromat path laundry_wq kworker nfs4_laundromat() nfsd4_end_grace() RECLAIM_COMPLETE path nfsd compound kthread nfsd4_reclaim_complete() inc_reclaim_complete() nfsd4_end_grace() Both callers can observe grace_ended == false on different CPUs, both store true, and both proceed into nfsd4_record_grace_done(), which invokes the active client_tracking_ops->grace_done callback. For tracking ops that drain reclaim_str_hashtbl (legacy_tracking_ops via nfsd4_recdir_purge_old, and the cld v1+ ops via nfsd4_cld_grace_done), grace_done calls nfs4_release_reclaim(), which walks every bucket of reclaim_str_hashtbl with no lock and calls nfs4_remove_reclaim_record() (list_del + kfree) on each entry. Two concurrent walkers corrupt the list and double-free every nfs4_client_reclaim. A concurrent nfsd4_find_reclaim_client() iterating the same bucket reads through freed memory. A third call site exists in nfs4_state_start_net() on the skip_grace startup path, but it runs under nfsd_mutex before any client has connected and before the laundromat's first delayed work fires, so it cannot race with the two callers above. Replace the scattered boolean fields in nfsd_net with a single unsigned long flags word and an enum nfsd_net_flag for the bit positions. The grace_ended race is fixed by using test_and_set_bit(), which is atomic on all architectures. The remaining flags (grace_end_forced, in_grace, somebody_reclaimed, track_reclaim_completes, nfsd_net_up, lockd_up) are converted to use test_bit/set_bit/clear_bit for consistency. This avoids sub-word cmpxchg issues on architectures like Hexagon that only support word-sized atomic operations.
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/netns.h
fs/nfsd/nfs4proc.c
fs/nfsd/nfs4recover.c
fs/nfsd/nfs4state.c
fs/nfsd/nfsctl.c
fs/nfsd/nfssvc.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, sidm
- 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-24 (24 days ago)source
- CVSS
- 8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.41%, higher than 33.6% 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 |
|---|---|---|
| 5.2 | 6.18.57 | 40bab0da844c |
| 5.2 | 7.2.4 | df5922fe09a8 |
| 5.2 | 7.3 | 11a5fe42e181 |
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
- nfsd4_end_grace() is reached from a remote NFSv4.1 RECLAIM_COMPLETE: svc_recv to nfsd_dispatch to nfsd4_proc_compound to nfsd4_sequence (sets cstate->clp) to nfsd4_reclaim_complete to inc_reclaim_complete to nfsd4_end_grace on TCP/2049. That RECLAIM_COMPLETE compound is the attacker-supplied protocol message.
- AC:HAttack complexity, high
- The other nfsd4_end_grace() caller is nfs4_laundromat() on laundry_wq, queued in nfs4_state_start_net() for nn->nfsd4_grace seconds. A peer cannot start that work (nfsd4_force_end_grace is only write_v4_end_grace). Both must see grace_ended==false, which needs an already-running grace with a non-empty reclaim_str_hashtbl the attacker cannot create on demand.
- PR:NPrivileges required, none
- Typical nfsd exports accept AUTH_SYS, so the client only asserts a uid. nfsd4_exchange_id() with SP4_NONE and nfsd4_create_session() are ALLOWED_AS_FIRST_OP without a filehandle, and OP_RECLAIM_COMPLETE is ALLOWED_WITHOUT_FH, so no fh_verify, share access, or Kerberos is required.
- UI:NUser interaction, none
- The attacker sends EXCHANGE_ID, CREATE_SESSION, SEQUENCE, and RECLAIM_COMPLETE on their own session. No write to v4_end_grace, mount, or other victim action is required.
- S:UScope, unchanged
- Concurrent nfs4_release_reclaim() list_del/kfree of nfs4_client_reclaim entries corrupts heap inside the host nfsd kernel. That stays in the same kernel security authority and is not a VM, IOMMU, or sandbox escape.
- C:HConfidentiality impact, high
- When two nfsd4_end_grace() callers both run nfsd4_record_grace_done() (nfsd4_cld_grace_done or nfsd4_recdir_purge_old), nfs4_release_reclaim() double-frees every nfs4_client_reclaim while nfsd4_find_reclaim_client() walks the same unlocked cr_strhash bucket through freed objects, a UAF read primitive.
- I:HIntegrity impact, high
- nfs4_remove_reclaim_record() does unlocked list_del(&crp->cr_strhash) then kfree on each nfs4_client_reclaim. Two concurrent walkers corrupt adjacent list pointers (unlink write) and double-free the slab objects, which is an arbitrary kernel write.
- A:HAvailability impact, high
- The same unlocked list_del/kfree in nfs4_release_reclaim(), or nfsd4_find_reclaim_client() following a freed cr_strhash, oopses the host kernel (poisoned list pointers or double-free of nfs4_client_reclaim), a full availability loss.