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-53398NFSD: Fix SECINFO_NO_NAME decode error cleanup

Description

In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix SECINFO_NO_NAME decode error cleanup nfsd4_decode_secinfo_no_name() currently initializes sin_exp after decoding sin_style. If the XDR stream is truncated, the decoder returns nfserr_bad_xdr before sin_exp is initialized. Since commit 3fdc54646234 ("NFSD: Reduce amount of struct nfsd4_compoundargs that needs clearing"), the inline iops array is not cleared between RPC calls. A failed SECINFO_NO_NAME decode can therefore leave sin_exp holding stale union contents from a previous operation. The error response path still invokes nfsd4_secinfo_no_name_release(), which calls exp_put() on a non-NULL sin_exp. Initialize sin_exp before the first failable decode step, matching nfsd4_decode_secinfo().

Timeline

  1. ID reserved

    By Linux

  2. · 40 days later

    Published

  3. · 3 months 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-53398, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.54% · top 54% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 5e76b25d7cc82c148d391c0c43b884e6427cb302 – < 8836405abdc53ca3dd5fc68b2cf6f8f012fad011
    • affected 07b68ff5c71cf4ed5443016d8eb116863c0a4d88 – < 49de5d31dd8fdebf78bdeaf196b0ca5cd5c75439
    • affected 3fdc546462348b8a497c72bc894e0cde9f10fc40 – < 5ec37edcb534f3fc92304be236d37f08e6545585
    • affected 3fdc546462348b8a497c72bc894e0cde9f10fc40 – < 1e04be34cafae119e82bcaccd6d28a20f72a3647
    • affected 3fdc546462348b8a497c72bc894e0cde9f10fc40 – < 161d1aaeb04d620d3692639700512bb5038c1e10
    • affected 3fdc546462348b8a497c72bc894e0cde9f10fc40 – < c8a24effd96d4779e2ad779654682304491c55a5
    • affected 3fdc546462348b8a497c72bc894e0cde9f10fc40 – < 46eb17d45be69d28c7a23ea03283b207426a8232
    • affected 3fdc546462348b8a497c72bc894e0cde9f10fc40 – < 9e18e83b8846a5c3fe13fc8a464b4865d33996c6
    • affected 5.10.220 – < 5.10.260
    • affected 5.15.154 – < 5.15.211
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 5.10.260 – ≤ 5.10.*
    • unaffected 5.15.211 – ≤ 5.15.*
    • unaffected 6.1.177 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.38 – ≤ 6.18.*
    • unaffected 7.1.3 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .