nfsd: reset write verifier on deferred writeback errors
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb · < 4367afc119c51e17a616f6908772b7e2c2c4013f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfsd: reset write verifier on deferred writeback errors
nfsd_vfs_write() and nfsd_commit() both call filemap_check_wb_err() to detect deferred writeback errors, but neither rotates the server's write verifier (nn->writeverf) when this check fails. Every other durable-storage-failure path in these functions calls commit_reset_write_verifier() before returning an error.
The missing rotation means clients holding UNSTABLE write data under the current verifier will COMMIT, receive the unchanged verifier back, and conclude their data is durable — silently dropping data that failed writeback. This violates the UNSTABLE+COMMIT durability contract (RFC 1813 §3.3.7, RFC 8881 §18.32).
Add commit_reset_write_verifier() calls at both filemap_check_wb_err() error sites, matching the pattern used by adjacent error paths in the same functions. The helper already filters -EAGAIN and -ESTALE internally, so the calls are unconditionally safe.
From the CVE record · Linux
Linux kernel nfsd fails to reset its write verifier when it detects a deferred writeback error. When an NFS client commits UNSTABLE write data after such an error, it may incorrectly conclude the data is durable, resulting in silent data loss. The input does not specify attacker access or user-interaction requirements.
Operators running Linux kernel NFS servers should check their installations; affected versions are not specified.