CVE-2026-53398

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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().

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 20, 2026

Advisory Details (8)

Auto-updated Jul 25, 2026
No patch confirmed yet.
generic

NFSD: Fix SECINFO_NO_NAME decode error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c8a24effd96d4779e2ad779654682304491c55a5
generic

NFSD: Fix SECINFO_NO_NAME decode error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e18e83b8846a5c3fe13fc8a464b4865d33996c6
generic

NFSD: Fix SECINFO_NO_NAME decode error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8836405abdc53ca3dd5fc68b2cf6f8f012fad011
generic

NFSD: Fix SECINFO_NO_NAME decode error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ec37edcb534f3fc92304be236d37f08e6545585
generic

NFSD: Fix SECINFO_NO_NAME decode error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49de5d31dd8fdebf78bdeaf196b0ca5cd5c75439
generic

NFSD: Fix SECINFO_NO_NAME decode error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46eb17d45be69d28c7a23ea03283b207426a8232
generic

NFSD: Fix SECINFO_NO_NAME decode error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e04be34cafae119e82bcaccd6d28a20f72a3647
generic

NFSD: Fix SECINFO_NO_NAME decode error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/161d1aaeb04d620d3692639700512bb5038c1e10

Vendor Advisories for CVE-2026-53398(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 22× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 09:34 UTCGHSA enrichment
  2. 2026-07-27 05:51 UTCGHSA enrichment
  3. 2026-07-27 02:06 UTCGHSA enrichment
  4. 2026-07-26 22:23 UTCGHSA enrichment
  5. 2026-07-26 18:38 UTCEG score recompute
  6. 2026-07-26 18:38 UTCGHSA enrichment
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:54 UTCGHSA enrichment
  9. 2026-07-26 11:10 UTCEG score recompute
  10. 2026-07-26 11:10 UTCGHSA enrichment
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-23 14:18 UTCEPSS rescore
  14. 2026-07-23 03:19 UTCEG score recompute
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-21 15:25 UTCEPSS rescore
  17. 2026-07-20 17:47 UTCEG score recompute
  18. 2026-07-20 17:47 UTCGHSA enrichment
  19. 2026-07-20 17:08 UTCEPSS rescore
  20. 2026-07-20 14:47 UTCEG score recompute▲ 9.80
  21. 2026-07-20 14:46 UTCGHSA enrichment
  22. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  23. 2026-07-19 12:26 UTCNVD update
  24. 2026-07-19 12:15 UTCEG score recompute
  25. 2026-07-19 12:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53398?
CVE-2026-53398 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix SECINFONONAME decode error cleanup nfsd4decodesecinfononame() currently initializes sin_exp after decoding sin_style. If the XDR stream is truncated, the decoder returns nfserrbadxdr before sin_exp is initialized. Since…
When was CVE-2026-53398 disclosed?
CVE-2026-53398 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53398 actively exploited?
CVE-2026-53398 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.2% of all scored CVEs.
What is the CVSS score of CVE-2026-53398?
CVE-2026-53398 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-53398?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53398, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53398

Explore →

Is Your Infrastructure Affected by CVE-2026-53398?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs