NFSD: Fix SECINFO_NO_NAME decode error cleanup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3fdc546462348b8a497c72bc894e0cde9f10fc40 · < c8a24effd96d4779e2ad779654682304491c55a5| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
Linux kernel NFSD can leave an export pointer holding stale contents when a truncated SECINFO_NO_NAME XDR request fails to decode. A network client that sends such an RPC request can trigger the error path to call exp_put() on that stale pointer; authentication requirements are not specified, and no user interaction is described.
Engineers running Linux kernels with NFSD should check their exposure; affected versions are not specified.