nfsd: initialize copy-notify stateid before publishing it
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 863b6e995665472f2af5be2436a874ab6a9e5ac6; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in d18d36395d973ef7372c8e6724970585f75b5c0b; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 4415a692346a39fdb647cbd717eda510159aaf55; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 9caad13b7cfe9ccb90cc405ac77335800e086595; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in e08a3dcaca0505f861e344a387f37f94d95dbdc2; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in a4d7fedcaaf33e60a01e53eafca9041ef966212f; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 4cdef96892f4fa6e70c405b6e8f2fd6972f3b64b; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 129643893b79f8a3c6b72045f933fbab5ee424ca
- Linux Linux
5.6
- KernelLinux
From 5.6.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/863b6e995665472f2af5be2436a874ab6a9e5ac6
- stable/c/d18d36395d973ef7372c8e6724970585f75b5c0b
- stable/c/4415a692346a39fdb647cbd717eda510159aaf55
- stable/c/9caad13b7cfe9ccb90cc405ac77335800e086595
- stable/c/e08a3dcaca0505f861e344a387f37f94d95dbdc2
- stable/c/a4d7fedcaaf33e60a01e53eafca9041ef966212f
- stable/c/4cdef96892f4fa6e70c405b6e8f2fd6972f3b64b
- stable/c/129643893b79f8a3c6b72045f933fbab5ee424ca