Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89699nfsd: validate symlink target length in NFSv4 CREATE

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89699, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Received3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.50% · top 57% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 36011308b3f01ce7dc9954f3cefcbb5291af9f95
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 888dad4b557352cf85be31613407b5ba51ad07d1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8661d3cb38fd148947e57dbc0871fd4d3fa33bbf
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3ef5e7a01a4d74995a65496bc9166d1e980a4355
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b24843ea3de1676b29902457b38507c95a80649b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 895a485cd3758031ef9993c0d53cf19ce8fb4ccc
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 45ec115cbfecb4b3cfab7fca6f73d1b60696a25a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 041f57056e5fb9c80adc088269322d2c61074406
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89699 badge
[![CVE-2026-89699](https://cveledger.app/badge/CVE-2026-89699.svg)](https://cveledger.app/cve/CVE-2026-89699)

Record last updated .