Linux
nfsd: Reset write verifier when async COPY writeback fails
In the Linux kernel, the following vulnerability has been resolved: nfsd: Reset write verifier when async COPY writeback fails Async COPY captures nn->writeverf at request time and reports it to the client via CB_OFFLOAD after the worker kthread completes. When the post-copy vfs_fsync_range() or filemap_check_wb_err() in _nfsd_copy_file_range() reports an error, the worker correctly leaves NFSD4_COPY_F_COMMITTED clear so that CB_OFFLOAD encodes wr_stable_how as NFS_UNSTABLE, but the server's write verifier is not rotated. A client that receives NFS_UNSTABLE in CB_OFFLOAD follows up with COMMIT to make the copied data durable. With the verifier unchanged, COMMIT returns the same value the client just received via CB_OFFLOAD, and the client concludes the copy is durable -- silently dropping the data whose writeback in fact failed. This violates the UNSTABLE+COMMIT durability contract (RFC 7862 section 15.1, RFC 8881 section 18.32) and matches the bug just fixed in nfsd_vfs_write() and nfsd_commit(). Rotate nn->writeverf at the writeback-failure site. The async COPY worker has no svc_rqst, so commit_reset_write_verifier() is not available here; calling nfsd_reset_write_verifier() directly mirrors the trace-less reset already used by nfsd_file_check_write_error() for the same purpose. Filter out -EAGAIN and -ESTALE, matching commit_reset_write_verifier(), since neither indicates a durable-storage failure.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 817c6eb975798647c4bbbfc9eb288aa413ec7f65, < cc5f7cef0659a27c13dd33edd8e2f79257b095c6
- >= eac0b17a77fbd763d305a5eaa4fd1119e5a0fe0d, < c6d2f6372c7e0f76b9c148ff7696aec64da0b5b7
- >= eac0b17a77fbd763d305a5eaa4fd1119e5a0fe0d, < 8a08ffe73eb2aa6bc6f88763da7e2b55bab6493a
- >= eac0b17a77fbd763d305a5eaa4fd1119e5a0fe0d, < 6b13d26cc21b6320a3c61d5e4cee2ce9a589b181
- >= eac0b17a77fbd763d305a5eaa4fd1119e5a0fe0d, < 31d4d0a62ec4bafbcdbad142f11ab1f90794b1d0
- >= eac0b17a77fbd763d305a5eaa4fd1119e5a0fe0d, < 591134e059e3456180244a826d6917cdc183140b
- >= eac0b17a77fbd763d305a5eaa4fd1119e5a0fe0d, < bf0cd31a9abcb728c17d79b4c2cc533612a8b6af
- >= eac0b17a77fbd763d305a5eaa4fd1119e5a0fe0d, < f5cb2276954cb80987a93ef9f9dfbfdbfc0f10b9
- >= 5.10.220, < 5.10.270
Fixed in cc5f7cef0659a27c13dd33edd8e2f79257b095c6, c6d2f6372c7e0f76b9c148ff7696aec64da0b5b7, 8a08ffe73eb2aa6bc6f88763da7e2b55bab6493a, 6b13d26cc21b6320a3c61d5e4cee2ce9a589b181, 31d4d0a62ec4bafbcdbad142f11ab1f90794b1d0, 591134e059e3456180244a826d6917cdc183140b, bf0cd31a9abcb728c17d79b4c2cc533612a8b6af, f5cb2276954cb80987a93ef9f9dfbfdbfc0f10b9, 5.10.270
- 5.14
Fixed in 0, 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3
Mitigation
Upgrade Linux to cc5f7cef0659a27c13dd33edd8e2f79257b095c6 or c6d2f6372c7e0f76b9c148ff7696aec64da0b5b7 or 8a08ffe73eb2aa6bc6f88763da7e2b55bab6493a or 6b13d26cc21b6320a3c61d5e4cee2ce9a589b181 or 31d4d0a62ec4bafbcdbad142f11ab1f90794b1d0 or 591134e059e3456180244a826d6917cdc183140b or bf0cd31a9abcb728c17d79b4c2cc533612a8b6af or f5cb2276954cb80987a93ef9f9dfbfdbfc0f10b9 or 5.10.270 or later.
Upgrade Linux to 0 or 5.10.270 or 5.15.221 or 6.1.188 or 6.6.157 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.