CVE-2026-89713 Linux CVE debrief

Who should care

Linux system administrators, security teams, and developers working with NFSD should assess exposure and prioritize patching or mitigation efforts. Linux system administrators and security teams should prioritize verifying exposure and applying patches or mitigations, focusing on systems with NFSD enabled. This includes verifying if NFSD is enabled on Linux systems, assessing exposure, and applying patches or mitigations provided by the Linux kernel [

Why it matters

A vulnerability in the Linux kernel's NFSD could allow a concurrent append operation to extend a file before the nfsd_setattr() function takes the inode lock, potentially leading to truncation without proper permission checks.

• Verify if NFSD is enabled and assess exposure to potential truncation operations
• Apply patches or mitigations to prevent unauthorized file modifications
• Monitor for potential truncation operations on files handled by NFSD

Technical summary

The vulnerability arises from a TOCTOU window in the nfsd_setattr() function, which could allow a concurrent append operation to extend a file before the function takes the inode lock, potentially leading to truncation without proper permission checks. The function first checks if a size update needs NFSD_MAY_TRUNC, but the comparison uses an unlocked read of the file size. This issue affects Linux system administrators and security teams, who should prioritize verifying exposure and applying patches or mitigations, focusing on systems with NFSD enabled. To address this, Linux system administrators and security teams should verify if NFSD is enabled and assess exposure to potential truncation operations. They

Defensive priority

Linux system administrators and security teams should prioritize verifying exposure and applying patches or mitigations, focusing on systems with NFSD enabled.

Recommended defensive actions

• Verify if NFSD is enabled on Linux systems and assess exposure
• Apply patches or mitigations provided by the Linux kernel maintainers
• Monitor for potential truncation operations on files handled by NFSD
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by a TOCTOU window in the nfsd_setattr() function. The function first checks if a size update needs NFSD_MAY_TRUNC, but the comparison uses an unlocked read of the file size. If a client sends a SETATTR that does not shrink the file at the time of the unlocked sample, a concurrent append can extend the file before nfsd_setattr() takes inode_lock().

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.