nfsd: validate nseconds in TIME_DELEG decode paths
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.507.2.47.3In the Linux kernel, the following vulnerability has been resolved:
nfsd: validate nseconds in TIME_DELEG decode paths
The xdrgen-based TIME_DELEG_ACCESS and TIME_DELEG_MODIFY decode arms store a raw uint32_t nseconds directly into tv_nsec without enforcing nseconds < NSEC_PER_SEC. The legacy nfsd4_decode_nfstime4 has this check but the TIME_DELEG paths do not. A malformed timespec can propagate through notify_change() to disk.
Add range checks in both nfs4xdr.c (SETATTR path) and nfs4callback.c (CB_GETATTR path).
From the CVE record · Linux
The Linux kernel's nfsd TIME_DELEG_ACCESS and TIME_DELEG_MODIFY decode paths do not check that nanoseconds are within the valid range. An attacker who can supply malformed TIME_DELEG values may cause invalid timestamps to propagate through notify_change() to disk. The input does not specify authentication requirements or user interaction.
Operators running the Linux kernel with nfsd should check whether their kernel includes the fix; affected versions are not specified.