CVE-2026-89684

CVE CVE-2026-89684EUVD EUVD-2026-76596Published 2026-09-11T19:46:06.000ZLast changed 2026-09-14T12:02:01.000ZCVSS 7.5

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 5.6; patch: 5.15.221; 624322f1adc58acd0b69f77a6ddc764207e97241 <8eeca993357a0bc35aaefebfd7462ac7b0a21d9a; patch: 6.6.157; 624322f1adc58acd0b69f77a6ddc764207e97241 <6ac469a274e3c7d87fc46ba46d83b95009680407; 624322f1adc58acd0b69f77a6ddc764207e97241 <a631a26a8777bb235eabd478bbbaf26a4db750bf; patch: 7.3-rc1; 624322f1adc58acd0b69f77a6ddc764207e97241 <be3a5c1d857b0dcbc11796cea603ef25834f75b2; patch: 0; 624322f1adc58acd0b69f77a6ddc764207e97241 <bfeac42d9074e539bacd1898dd8c14b7f5776620; patch: 6.18.50; patch: 6.12.109; 624322f1adc58acd0b69f77a6ddc764207e97241 <21d6c5957f5ca97d7352e60f55ea412beb9419f5; 624322f1adc58acd0b69f77a6ddc764207e97241 <c7270f62e7a05a2ee68aa2b74262b658a14463bd; 624322f1adc58acd0b69f77a6ddc764207e97241 <63e18fc65587fd3f7b4c6d70e96d32fc41d82ba3; patch: 6.1.188; patch: 7.2.4; patch: 5.10.270

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.