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-89673

nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo nfsd4_ff_encode_getdeviceinfo() computes the da_addr_body reservation as 16 + netid_len + addr_len, but the subsequent xdr_encode_opaque() calls emit 8 + round_up(netid_len, 4) + round_up(addr_len, 4) bytes. The mismatch means the declared da_addr_body length exceeds the actual encoded data by 2-8 bytes on every flexfile GETDEVICEINFO reply, leaking stale reply-page content to the client and mis-aligning the subsequent version list decode. Use xdr_align_size() for each string length to match what xdr_encode_opaque() actually writes.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 43 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 3f1a2b0b2d575f39ff0bedb5411822fe7446a805 – < 356decf074b82bac5564568203c12426dcea3470
    • affected 19a648a07572c70fbe16faf0fafaf3dce9fd998a – < 15460c8e6c9bc92cda8f68bc419ac082300ab3d6
    • affected 6d08bd22fa2941a4d5ef45ed115dd00e484a93d7 – < 9be67a6be48ddf2ebaa98c0df671690b8f9666e7
    • affected 6372e2ee629894433fe6107d7048536a3280a284 – < 88bce7e326c368d7df15126ccac537e54bebd467
    • affected 6372e2ee629894433fe6107d7048536a3280a284 – < 74015b7be806ad9e21d46f7bd2831df280c6c783
    • affected 6372e2ee629894433fe6107d7048536a3280a284 – < 41ebca28e17f84293650598f86bd69532ec1a8e0
    • affected 6372e2ee629894433fe6107d7048536a3280a284 – < 62e5949f0dd5ec837af144860ff908369df4c7c9
    • affected 6372e2ee629894433fe6107d7048536a3280a284 – < 8b989aaec85e1293a871d602590c951fe44b8647
    • affected 82e36f0c287769a0430268739a71dbd56df0e679
    • affected 6370e66a71c4869247f8f406c2a8b2c43df8998f
    • affected 16282aeca44bfac0d1ac3be6cd1a719d6ff3d749
    • affected efcae97fa425ca6db9d126e37daccf2d7225cb09
    • affected 64c959d59c24c661bd5338e4e6f1f703d7c309a1
    • affected 5.10.195 – < 5.10.270
    • affected 5.15.132 – < 5.15.221
    • affected 6.1.53 – < 6.1.188
    • affected 4.14.326 – < 4.15
    • affected 4.19.295 – < 4.20
    • affected 5.4.257 – < 5.5
    • affected 6.4.16 – < 6.5
    • affected 6.5.3 – < 6.6
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • 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-89673 badge
[![CVE-2026-89673](https://cveledger.app/badge/CVE-2026-89673.svg)](https://cveledger.app/cve/CVE-2026-89673)

Record last updated .