NFSD: fix use-after-free on source server when doing inter-server copy
- 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.150, 5.15.75, 5.19.17, 6.0.3
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: NFSD: fix use-after-free on source server when doing inter-server copy Use-after-free occurred when the laundromat tried to free expired cpntf_state entry on the s2s_cp_stateids list after inter-server copy completed. The sc_cp_list that the expired copy state was inserted on was already freed. When COPY completes, the Linux client normally sends LOCKU(lock_state x), FREE_STATEID(lock_state x) and CLOSE(open_state y) to the source server. The nfs4_put_stid call from nfsd4_free_stateid cleans up the copy state from the s2s_cp_stateids list before freeing the lock state's stid. However, sometimes the CLOSE was sent before the FREE_STATEID request. When this happens, the nfsd4_close_open_stateid call from nfsd4_close frees all lock states on its st_locks list without cleaning up the copy state on the sc_cp_list list. When the time the FREE_STATEID arrives the server returns BAD_STATEID since the lock state was freed. This causes the use-after-free error to occur when the laundromat tries to free the expired cpntf_state. This patch adds a call to nfs4_free_cpntf_statelist in nfsd4_close_open_stateid to clean up the copy state before calling free_ol_stateid_reaplist to free the lock state's stid on the reaplist.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in bbacfcde5fff25ac22597e8373a065c647da6738; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 83b94969751a691347606dbe6b1865efcfa5a643; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 6ea71246b7a02af675d733e72d14bd0d591d5f4a; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 35aa0fb8c3033a3d78603356e96fc18c5b9cceb2; From 624322f1adc58acd0b69f77a6ddc764207e97241 · fixed in 019805fea91599b22dfa62ffb29c022f35abeb06
- Linux Linux
5.6
- KernelLinux
From 5.6.0 · fixed in 5.10.150; From 5.11.0 · fixed in 5.15.75; From 5.16.0 · fixed in 5.19.17; From 5.20.0 · fixed in 6.0.3