nfsd: fix cpntf publish race in nfs4_init_cp_state
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel c7270f62e7a05a2ee68aa2b74262b658a14463bd, Kernel 21d6c5957f5ca97d7352e60f55ea412beb9419f5, Kernel 63e18fc65587fd3f7b4c6d70e96d32fc41d82ba3 and 12 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=624322f1adc58acd0b69f77a6ddc764207e97241 <c7270f62e7a05a2ee68aa2b74262b658a14463bd, >=624322f1adc58acd0b69f77a6ddc764207e97241 <21d6c5957f5ca97d7352e60f55ea412beb9419f5, >=624322f1adc58acd0b69f77a6ddc764207e97241 <63e18fc65587fd3f7b4c6d70e96d32fc41d82ba3, >=624322f1adc58acd0b69f77a6ddc764207e97241 <6ac469a274e3c7d87fc46ba46d83b95009680407, >=624322f1adc58acd0b69f77a6ddc764207e97241 <8eeca993357a0bc35aaefebfd7462ac7b0a21d9a, >=624322f1adc58acd0b69f77a6ddc764207e97241 <a631a26a8777bb235eabd478bbbaf26a4db750bf, >=624322f1adc58acd0b69f77a6ddc764207e97241 <be3a5c1d857b0dcbc11796cea603ef25834f75b2, >=624322f1adc58acd0b69f77a6ddc764207e97241 <bfeac42d9074e539bacd1898dd8c14b7f5776620, =5.6 | c7270f62e7a05a2ee68aa2b74262b658a14463bd, 21d6c5957f5ca97d7352e60f55ea412beb9419f5, 63e18fc65587fd3f7b4c6d70e96d32fc41d82ba3, 6ac469a274e3c7d87fc46ba46d83b95009680407, 8eeca993357a0bc35aaefebfd7462ac7b0a21d9a, a631a26a8777bb235eabd478bbbaf26a4db750bf, be3a5c1d857b0dcbc11796cea603ef25834f75b2, bfeac42d9074e539bacd1898dd8c14b7f5776620 |
| linux-kernel: Kernel | >=5.16.0 <6.1.188, >=5.6.0 <5.10.270, >=6.13.0 <6.18.50, >=6.19.0 <7.2.4, >=6.2.0 <6.6.157, >=6.7.0 <6.12.109, >=5.11.0 <5.15.221 | 6.1.188, 5.10.270, 6.18.50, 7.2.4, 6.6.157, 6.12.109, 5.15.221 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket