CVE-2026-89669

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.7%
Linux•Linux•Versions : 6.12.109, <=6.1.*, <=6.12.*, <129643893b79f8a3c6b72045f933fbab5ee424ca, 5.15.221, 5.10.270, 0, 7.2.4, 6.1.188, 5.6, <=5.10.*, <=6.6.*, 6.6.157, <4415a692346a39fdb647cbd717eda510159aaf55, <=6.18.*, 624322f1adc58acd0b69f77a6ddc764207e97241, <=7.2.*, <5.6, <9caad13b7cfe9ccb90cc405ac77335800e086595, <=*, <d18d36395d973ef7372c8e6724970585f75b5c0b, <=5.15.*, <e08a3dcaca0505f861e344a387f37f94d95dbdc2, <a4d7fedcaaf33e60a01e53eafca9041ef966212f, 6.18.50, <4cdef96892f4fa6e70c405b6e8f2fd6972f3b64b, <863b6e995665472f2af5be2436a874ab6a9e5ac6, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: initialize copy-notify stateid before publishing it nfsd4_copy_notify() finished initializing the cpntf state after nfs4_alloc_init_cpntf_state() had already linked it into the s2s_cp_stateids IDR and the parent's sc_cp_list, with cs_count == 1 (the membership reference) and none held for the caller. A racing OFFLOAD_CANCEL (crafted cl_id == nn->s2s_cp_cl_id plus the guessable so_id) could reach manage_cpntf_state() and free the entry, turning the caller's subsequent cpn_cnr_stateid read and cp_p_stateid/cp_p_clid writes into use-after-free. The owning clientid was also only recorded after publication, so it could not gate an ownership check in that window. Record cp_p_stateid and cp_p_clid inside nfs4_alloc_init_cpntf_state() before nfs4_init_cp_state() publishes the entry, and return it with an extra reference. The caller reads the stateid under that reference and drops it with nfs4_put_cpntf_state(); on a late error the laundromat reaps the entry.

Gravité et risque d'exploitation

CVE-2026-89669 obtient un score CVSS de 9.8/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.69 %, ce qui la place devant 52.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.12.109, <=6.1.*, <=6.12.*, <129643893b79f8a3c6b72045f933fbab5ee424ca, 5.15.221, 5.10.270, 0, 7.2.4, 6.1.188, 5.6, <=5.10.*, <=6.6.*, 6.6.157, <4415a692346a39fdb647cbd717eda510159aaf55, <=6.18.*, 624322f1adc58acd0b69f77a6ddc764207e97241, <=7.2.*, <5.6, <9caad13b7cfe9ccb90cc405ac77335800e086595, <=*, <d18d36395d973ef7372c8e6724970585f75b5c0b, <=5.15.*, <e08a3dcaca0505f861e344a387f37f94d95dbdc2, <a4d7fedcaaf33e60a01e53eafca9041ef966212f, 6.18.50, <4cdef96892f4fa6e70c405b6e8f2fd6972f3b64b, <863b6e995665472f2af5be2436a874ab6a9e5ac6, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références