GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel nfsd: broken short-write detection writes the next segment at the wrong file offset

CVSS 7.5CVE-2026-89678Kernel, userspace & hypervisorcurated

Impact

The partial-write check compares the bytes written against the already-advanced residual count, so the loop only breaks when less than half a segment was written. Any short write between 50% and 99% slips through: the next segment is written at an offset that was only bumped by the short amount, and the byte count reported to the client is too high. This is silent data corruption on the server side, and it is the one entry in this batch scored for integrity rather than availability. On a GPU fleet the files at risk are checkpoints and dataset shards - corruption that surfaces days later as a failed restore, not as an alert.

Who can reach it

No attacker is required; it triggers whenever a write on the NFS server's direct-I/O path completes short. Any NFS client writing to an affected export can be the one whose data lands wrong. Authentication is whatever the export requires.

What to do

Update the host kernel to a stable release that snapshots the segment byte count before the write, then reboot the NFS server. If the fleet ran an affected kernel under load, verify checksums on checkpoints and datasets written in that period - the corruption is silent and patching does not repair already-written files.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.