SECUFOCUSNOW
Home›CVE index›CVE-2026-53398
Review reviewCritical

CVE-2026-53398

Linux Linux, linux kernel

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 s...

CVSS
9.8
EPSS
0.51%
40.8% percentile
CISA KEV
Not listed
Published
2026.07.19
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.51%
Technical severityCVSS 9.8

Vulnerability overview

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 s...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 5e76b25d7cc82c148d391c0c43b884e6427cb302 < 8836405abdc53ca3dd5fc68b2cf6f8f012fad011, >= 07b68ff5c71cf4ed5443016d8eb116863c0a4d88 < 49de5d31dd8fdebf78bdeaf196b0ca5cd5c75439, >= 3fdc546462348b8a497c72bc894e0cde9f10fc40 < 5ec37edcb534f3fc92304be236d37f08e6545585, >= 3fdc546462348b8a497c72bc894e0cde9f10fc40 < 1e04be34cafae119e82bcaccd6d28a20f72a3647, >= 3fdc546462348b8a497c72bc894e0cde9f10fc40 < 161d1aaeb04d620d3692639700512bb5038c1e10, >= 3fdc546462348b8a497c72bc894e0cde9f10fc40 < c8a24effd96d4779e2ad779654682304491c55a5, >= 3fdc546462348b8a497c72bc894e0cde9f10fc40 < 46eb17d45be69d28c7a23ea03283b207426a8232, >= 3fdc546462348b8a497c72bc894e0cde9f10fc40 < 9e18e83b8846a5c3fe13fc8a464b4865d33996c6, >= 5.10.220 < 5.10.260, >= 5.15.154 < 5.15.211, >= 6.1, >= 6.1 < 6.1.177, >= 6.2 < 6.6.144, >= 6.7 < 6.12.95, >= 6.13 < 6.18.38, >= 6.19 < 7.1.3
Fixed versions
5.10.260, 5.15.211, 6.1.177, 6.6.144, 6.12.95, 6.18.38, 7.1.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
Not available