NFS: fix an incorrect limit in filelayout_decode_layout()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 16b374ca439fb406e46e071f75428f5b033056f8 · < 9b367fe770b1b80d7bf64ed0d177544a44405f6e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
NFS: fix an incorrect limit in filelayout_decode_layout()
The "sizeof(struct nfs_fh)" is two bytes too large and could lead to memory corruption. It should be NFS_MAXFHSIZE because that's the size of the ->data[] buffer.
I reversed the size of the arguments to put the variable on the left.
From the CVE record · Linux
The Linux kernel's NFS filelayout_decode_layout() uses a limit two bytes larger than the file handle data buffer, which could lead to memory corruption. The input does not specify how an attacker could trigger the issue or whether access, authentication, or user interaction is required.
Engineers running Linux kernels with NFS support should check their deployments; affected versions are not specified.