CVE-2026-89669

nfsd: initialize copy-notify stateid before publishing it

CRITICAL
9.8
CVSS Score
Published: September 11, 2026 at 07:45 PM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
CRITICAL9.8
Exploit prediction
EPSS 0.7%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.6624322f1adc58acd0b69f77a6ddc764207e97241
Vendor states this is fixed in 129643893b79f8a3c6b72045f933fbab5ee424ca (fixed)
Vendor states this is fixed in 4415a692346a39fdb647cbd717eda510159aaf55 (fixed)
Vendor states this is fixed in 4cdef96892f4fa6e70c405b6e8f2fd6972f3b64b (fixed)
Vendor states this is fixed in 863b6e995665472f2af5be2436a874ab6a9e5ac6 (fixed)
Vendor states this is fixed in 9caad13b7cfe9ccb90cc405ac77335800e086595 (fixed)
Vendor states this is fixed in a4d7fedcaaf33e60a01e53eafca9041ef966212f (fixed)
Vendor states this is fixed in d18d36395d973ef7372c8e6724970585f75b5c0b (fixed)
Vendor states this is fixed in e08a3dcaca0505f861e344a387f37f94d95dbdc2 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

9.8CRITICALLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card