PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-89699 Linux CVE debrief

A vulnerability in the Linux kernel's nfsd has been addressed, where an attacker could have forced an allocation of up to the maximum RPC payload size for a symlink target in an NFSv4 CREATE operation. This issue has been resolved by adding validation for the symlink target length. The vulnerability could allow an attacker to force large allocations for symlink targets in NFSv4 CREATE operations. Defenders should prioritize verifying and applying patches, assessing exposure for systems using NFSv4, and monitoring for potential exploitation attempts.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-11
Original CVE updated
2026-10-19
Advisory published
2026-09-11
Advisory updated
2026-10-19

Who should care

Defenders responsible for Linux systems using NFSv4 should assess exposure and prioritize patching. This includes system administrators, security teams, and IT professionals managing Linux-based infrastructure. They should review system configurations, monitor for potential exploitation attempts, and implement compensating controls where necessary.

Why it matters

This vulnerability in the Linux kernel's nfsd could allow an attacker to force large allocations for symlink targets in NFSv4 CREATE operations. Defenders should prioritize verifying and applying patches, assessing exposure for systems using NFSv4, and monitoring for potential exploitation attempts.

  • Verify and prioritize patching for affected Linux kernel versions
  • Assess exposure for systems using NFSv4
  • Monitor for potential exploitation attempts

Technical summary

The Linux kernel's nfsd did not validate symlink target lengths in NFSv4 CREATE operations, allowing for large allocations. This has been fixed by adding validation for cr_datalen in nfsd4_decode_create(). The fix prevents clients from forcing large allocations and reduces the risk of denial-of-service attacks. The vulnerability was publicly disclosed and addressed through a Linux kernel commit, which has been verified through official CVE and NVD records, as well as Linux kernel commit records, confirming the fix has been implemented.

Defensive priority

Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability, particularly for systems that use NFSv4.

Recommended defensive actions

  • Verify and apply patches for Linux kernel versions affected by this vulnerability
  • Review system configurations for NFSv4 usage and assess exposure
  • Monitor system logs for potential exploitation attempts
  • Perform vulnerability scanning to identify potentially affected systems
  • Implement compensating controls for exposed systems while remediation is scheduled and verified
  • Track exceptions and retest remediated assets to ensure patching effectiveness
  • Review and update incident response plans to account for potential exploitation

Evidence notes

The CVE Program record and NVD vulnerability detail provide official information on this vulnerability. Linux kernel commit records show the fix has been implemented. The vulnerability was addressed by adding validation for cr_datalen in nfsd4_decode_create(). The fix bounds the allocation and prevents potential denial-of-service attacks.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-89699 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-89699

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-89699 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-89699

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • nfsd: validate symlink target length in NFSv4 CREATE

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/89xxx/CVE-2026-89699.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/36011308b3f01ce7dc9954f3cefcbb5291af9f95

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/888dad4b557352cf85be31613407b5ba51ad07d1

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/8661d3cb38fd148947e57dbc0871fd4d3fa33bbf

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/3ef5e7a01a4d74995a65496bc9166d1e980a4355

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b24843ea3de1676b29902457b38507c95a80649b

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/895a485cd3758031ef9993c0d53cf19ce8fb4ccc

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/45ec115cbfecb4b3cfab7fca6f73d1b60696a25a

    Supplemental source

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.