CVE-2026-53393: Linux kernel · nfsd: reset write verifier on deferred writeback errors
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in bc2baca02ec56da7707a74ed5d340b0a1dff1841 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in bc2baca02ec56da7707a74ed5d340b0a1dff1841, b027cca33c97354149fcc0ddeede4525c41093cd, b8e5894e56cff70fa245628fe16f0ad6367f8090 +7
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/b8e5894e56cff70fa245628fe16f0ad6367f8090 (opens in a new tab)
- git.kernel.org/stable/c/bc2baca02ec56da7707a74ed5d340b0a1dff1841 (opens in a new tab)
- git.kernel.org/stable/c/43b65d2997963e80e8d8d86520bcb1e0751227de (opens in a new tab)
- git.kernel.org/stable/c/666e837b247fcadf2d8d508b9b0e49d720393eb4 (opens in a new tab)
- git.kernel.org/stable/c/1dd664b39774a9c89b72de8e59bf9ef4b3aaff2e (opens in a new tab)
- git.kernel.org/stable/c/4367afc119c51e17a616f6908772b7e2c2c4013f (opens in a new tab)
- git.kernel.org/stable/c/b027cca33c97354149fcc0ddeede4525c41093cd (opens in a new tab)
- git.kernel.org/stable/c/2090b05803faab8a9fa62fbff871007862cac1b7 (opens in a new tab)