nfsd: fix cpntf publish race in nfs4_init_cp_state
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix cpntf publish race in nfs4_init_cp_state nfs4_alloc_init_cpntf_state() published the new cpntf entry into the s2s_cp_stateids IDR (with cs_type set) in one s2s_cp_lock section, then took the lock again to list_add() it onto p_stid->sc_cp_list. In the gap the entry is reachable by so_id but cp_list is still {NULL,NULL} from kzalloc. A racing OFFLOAD_CANCEL (so_id is echoed to the client as cnr_stateid, so any NFSv4.2 client can drive it) reaches manage_cpntf_state() -> _free_cpntf_state_locked() and does list_del() on the zeroed list_head, oopsing the server. Fold the cs_type assignment and the list_add() into the same critical section as idr_alloc_cyclic(), so a concurrent lookup either misses the entry or sees a fully linked cp_list. INIT_LIST_HEAD() the entry after allocation and switch _free_cpntf_state_locked() to list_del_init() so a stale unlink is a no-op. nfs4_init_copy_state() passes NULL p_stid and skips the list_add, preserving NFS4_COPY_STID semantics.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 63e18fc65587fd3f7b4c6d70e96d32fc41d82ba3; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 6ac469a274e3c7d87fc46ba46d83b95009680407; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 8eeca993357a0bc35aaefebfd7462ac7b0a21d9a; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in bfeac42d9074e539bacd1898dd8c14b7f5776620; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 21d6c5957f5ca97d7352e60f55ea412beb9419f5; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in a631a26a8777bb235eabd478bbbaf26a4db750bf; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in c7270f62e7a05a2ee68aa2b74262b658a14463bd; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in be3a5c1d857b0dcbc11796cea603ef25834f75b2
- Linux Linux
5.6
- KernelLinux
From 5.6.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/63e18fc65587fd3f7b4c6d70e96d32fc41d82ba3
- stable/c/6ac469a274e3c7d87fc46ba46d83b95009680407
- stable/c/8eeca993357a0bc35aaefebfd7462ac7b0a21d9a
- stable/c/bfeac42d9074e539bacd1898dd8c14b7f5776620
- stable/c/21d6c5957f5ca97d7352e60f55ea412beb9419f5
- stable/c/a631a26a8777bb235eabd478bbbaf26a4db750bf
- stable/c/c7270f62e7a05a2ee68aa2b74262b658a14463bd
- stable/c/be3a5c1d857b0dcbc11796cea603ef25834f75b2