CVE-2026-53398

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM 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

A fix is available — apply it.

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(medium)
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
44%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Sep 7, 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.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-08ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-08ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-08ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.3-1—

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 232× 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.

Showing the most recent 100 of 395 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-08 03:32 UTCVendor advisory
  5. 2026-09-08 03:32 UTCGHSA enrichment
  6. 2026-09-07 23:46 UTCEG score recompute
  7. 2026-09-07 23:46 UTCVendor advisory
  8. 2026-09-07 23:46 UTCGHSA enrichment
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 17:05 UTCEG score recompute
  11. 2026-09-06 17:05 UTCVendor advisory
  12. 2026-09-06 17:04 UTCGHSA enrichment
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 13:17 UTCVendor advisory
  15. 2026-09-06 13:17 UTCGHSA enrichment
  16. 2026-09-06 04:29 UTCVendor advisory
  17. 2026-09-06 04:29 UTCGHSA enrichment
  18. 2026-09-06 00:29 UTCVendor advisory
  19. 2026-09-06 00:29 UTCGHSA enrichment
  20. 2026-09-05 20:21 UTCEG score recompute
  21. 2026-09-05 20:21 UTCVendor advisory
  22. 2026-09-05 20:21 UTCGHSA enrichment
  23. 2026-09-04 05:06 UTCEPSS rescore
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-01 13:54 UTCEPSS rescore
Show 75 more
  1. 2026-09-01 04:40 UTCEPSS rescore
  2. 2026-08-31 06:54 UTCVendor advisory
  3. 2026-08-31 06:54 UTCGHSA enrichment
  4. 2026-08-31 02:55 UTCVendor advisory
  5. 2026-08-31 02:55 UTCGHSA enrichment
  6. 2026-08-30 23:11 UTCVendor advisory
  7. 2026-08-30 23:11 UTCGHSA enrichment
  8. 2026-08-30 19:27 UTCEG score recompute
  9. 2026-08-30 19:27 UTCVendor advisory
  10. 2026-08-30 19:27 UTCGHSA enrichment
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 15:44 UTCVendor advisory
  13. 2026-08-30 15:44 UTCGHSA enrichment
  14. 2026-08-30 10:58 UTCVendor advisory
  15. 2026-08-30 10:58 UTCGHSA enrichment
  16. 2026-08-30 06:56 UTCVendor advisory
  17. 2026-08-30 06:56 UTCGHSA enrichment
  18. 2026-08-30 03:04 UTCEG score recompute
  19. 2026-08-30 03:04 UTCVendor advisory
  20. 2026-08-30 03:04 UTCGHSA enrichment
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-28 01:46 UTCVendor advisory
  24. 2026-08-28 01:46 UTCGHSA enrichment
  25. 2026-08-27 21:25 UTCEG score recompute
  26. 2026-08-27 21:25 UTCVendor advisory
  27. 2026-08-27 21:25 UTCGHSA enrichment
  28. 2026-08-27 14:25 UTCEPSS rescore
  29. 2026-08-27 11:59 UTCVendor advisory
  30. 2026-08-27 11:59 UTCGHSA enrichment
  31. 2026-08-27 02:12 UTCVendor advisory
  32. 2026-08-27 02:12 UTCGHSA enrichment
  33. 2026-08-26 22:29 UTCEG score recompute
  34. 2026-08-26 22:29 UTCVendor advisory
  35. 2026-08-26 22:29 UTCGHSA enrichment
  36. 2026-08-26 14:46 UTCEPSS rescore
  37. 2026-08-26 11:46 UTCVendor advisory
  38. 2026-08-26 11:46 UTCGHSA enrichment
  39. 2026-08-26 07:25 UTCVendor advisory
  40. 2026-08-26 07:25 UTCGHSA enrichment
  41. 2026-08-26 02:29 UTCVendor advisory
  42. 2026-08-26 02:29 UTCGHSA enrichment
  43. 2026-08-25 22:46 UTCVendor advisory
  44. 2026-08-25 22:46 UTCGHSA enrichment
  45. 2026-08-25 18:49 UTCVendor advisory
  46. 2026-08-25 18:49 UTCGHSA enrichment
  47. 2026-08-25 14:32 UTCEG score recompute
  48. 2026-08-25 14:32 UTCVendor advisory
  49. 2026-08-25 14:32 UTCGHSA enrichment
  50. 2026-08-25 13:49 UTCEPSS rescore
  51. 2026-08-25 10:29 UTCVendor advisory
  52. 2026-08-25 10:29 UTCGHSA enrichment
  53. 2026-08-25 06:46 UTCGHSA enrichment
  54. 2026-08-25 02:38 UTCVendor advisory
  55. 2026-08-25 02:38 UTCGHSA enrichment
  56. 2026-08-24 22:55 UTCVendor advisory
  57. 2026-08-24 22:55 UTCGHSA enrichment
  58. 2026-08-24 19:12 UTCEG score recompute
  59. 2026-08-24 19:12 UTCVendor advisory
  60. 2026-08-24 19:12 UTCGHSA enrichment
  61. 2026-08-24 12:51 UTCEG score recompute
  62. 2026-08-24 12:51 UTCVendor advisory
  63. 2026-08-24 12:51 UTCGHSA enrichment
  64. 2026-08-24 09:08 UTCVendor advisory
  65. 2026-08-24 09:08 UTCGHSA enrichment
  66. 2026-08-24 05:18 UTCVendor advisory
  67. 2026-08-24 05:18 UTCGHSA enrichment
  68. 2026-08-24 01:35 UTCVendor advisory
  69. 2026-08-24 01:35 UTCGHSA enrichment
  70. 2026-08-23 21:48 UTCVendor advisory
  71. 2026-08-23 21:48 UTCGHSA enrichment
  72. 2026-08-23 18:05 UTCVendor advisory
  73. 2026-08-23 18:05 UTCGHSA enrichment
  74. 2026-08-23 14:22 UTCVendor advisory
  75. 2026-08-23 14:22 UTCGHSA enrichment

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 August 17, 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 56.1% 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

See which npm, PyPI, Go, and Maven packages are affected by 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