{"id":21585,"date":"2026-09-12T04:31:23","date_gmt":"2026-09-11T20:31:23","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-89663"},"modified":"2026-09-12T04:31:23","modified_gmt":"2026-09-11T20:31:23","slug":"cve-2026-89663","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-89663","title":{"rendered":"CVE-2026-89663 &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: revoke copy-not"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>nfsd: revoke copy-notify stateids before dropping their reference<\/p>\n<p>Copy-notify stateids live in the s2s_cp_stateids IDR and on their parent<br \/>\nstid&#8217;s sc_cp_list, pinned by a single membership reference.<br \/>\n_free_cpntf_state_locked() only unlinks an entry once its refcount reaches<br \/>\nzero, so any revoke path that runs while a concurrent<br \/>\nfind_cpntf_state()\/manage_cpntf_state() holder has elevated cs_count drops<br \/>\nthe reference without unlinking, leaving the entry discoverable with its<br \/>\nmembership reference already consumed. A second revoke or a laundromat tick<br \/>\nthen frees it while the reader still holds the pointer &#8212; a<br \/>\nKASAN-detectable use-after-free at the reader&#8217;s nfs4_put_cpntf_state().<\/p>\n<p>This affected all three revoke paths:<\/p>\n<p>  &#8211; The parent-stid drain (nfs4_free_cpntf_statelist()) repeatedly called<br \/>\n    _free_cpntf_state_locked() on the first list entry; a holder that had<br \/>\n    bumped cs_count made it return early, so the next iteration<br \/>\n    re-decremented and burned the holder&#8217;s reference.<\/p>\n<p>  &#8211; OFFLOAD_CANCEL (manage_cpntf_state()) and laundromat expiry likewise<br \/>\n    used _free_cpntf_state_locked() and could drop 2-&gt;1 without unlinking.<\/p>\n<p>Add revoke_cpntf_state_locked(), which unhashes the entry from the IDR and<br \/>\nsc_cp_list first (deferring the final free to any holder), and use it from<br \/>\nall three revoke paths. The drain now walks with list_for_each_entry_safe()<br \/>\nand revokes each entry unconditionally, so it terminates in one pass per<br \/>\nentry regardless of cs_count. The unhash is gated on<br \/>\n!list_empty(&amp;cps-&gt;cp_list); the idr_remove() gate matters because<br \/>\nidr_alloc_cyclic() may have recycled the so_id by then. Keep<br \/>\n_free_cpntf_state_locked() for the reference-holder put path only, where a<br \/>\nconcurrent revoke may already have unlinked the entry (its list_del_init()<br \/>\nthen a no-op).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>nfsd: revoke copy-notify stateids before dropping their reference<\/p>\n<p>Copy-notify stateids live in the s2s_cp_stateids IDR and on thei<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-21585","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/21585","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=21585"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=21585"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=21585"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}