Vulnerability · CVE-2026-89699
nfsd: validate symlink target length in NFSv4 CREATE
Published Sep 11, 2026 · catalog updated Oct 17, 2026 · nfsd: validate symlink target
Check if you run it
No confirmed exploitation is on record for CVE-2026-89699. EPSS is 0.50%. Act only if a listed version of nfsd: validate symlink target is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (nfsd: validate symlink target).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.50%
- Remediation
- Not established
- Affected products
- Linux Kernel
In the Linux kernel, the following vulnerability has been resolved: nfsd: validate symlink target length in NFSv4 CREATE nfsd4_decode_create() accepts an unbounded cr_datalen from the wire for NF4LNK symlink targets, allowing a client to force a kmalloc of up to the maximum RPC payload size (several MiB) per COMPOUND op that persists until compound teardown. The VFS rejects oversized targets with ENAMETOOLONG, but the allocation has already occurred. Reject cr_datalen == 0 early with nfserr_inval and cr_datalen greater than NFS4_MAXPATHLEN (PATH_MAX) with nfserr_nametoolong to bound the allocation.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Linux Kernel2.6.12 → 5.10.270; 5.11.0 → 5.15.221; 5.16.0 → 6.1.188
How to fix CVE-2026-89699
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-89699. EPSS is 0.50%. Act only if a listed version of nfsd: validate symlink target is installed.
Which versions are affected?
Compare what you have installed with Kernel 2.6.12 → 5.10.270; 5.11.0 → 5.15.221; 5.16.0 → 6.1.188. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.50%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 11, 2026 · OpenSSF OSV / OSV Scanner
Detected
In the Linux kernel, the following vulnerability has been resolved: nfsd: validate symlink target length in NFSv4 CREATE nfsd4_decode_create() accepts an unbounded cr_datalen from the wire for NF4LNK symlink targets, allowing a client to force a kmalloc of up to the maximum RPC payload size (several MiB) per COMPOUND op that persists until compound teardown. The VFS rejects oversized targets with
Oct 17, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 5.10.270; Kernel fixed in 5.15.221; Kernel fixed in 6.1.188; Kernel fixed in 6.6.157
Oct 17, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 5.10.270; 5.11.0
Oct 17, 2026 · OpenSSF OSV / OSV Scanner
Updated
In the Linux kernel, the following vulnerability has been resolved: nfsd: validate symlink target length in NFSv4 CREATE nfsd4_decode_create() accepts an unbounded cr_datalen from the wire for NF4LNK symlink targets, allowing a client to force a kmalloc of up to the maximum RPC payload size (several MiB) per COMPOUND op that persists until compound teardown. The VFS rejects oversized targets with
Sources
- CVE.orgVulnerability recordCVE-2026-89699
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-89699
30-day exploitation probability 0.5%
first.org - OpenSSF OSV / OSV ScannerPackage advisoryCVE-2026-89699
nfsd: validate symlink target length in NFSv4 CREATE
osv.dev
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.