nfs: pass explicit offset/count to trace events
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.6.1306.10.36.11In the Linux kernel, the following vulnerability has been resolved:
nfs: pass explicit offset/count to trace events
nfs_folio_length is unsafe to use without having the folio locked and a check for a NULL ->f_mapping that protects against truncations and can lead to kernel crashes. E.g. when running xfstests generic/065 with all nfs trace points enabled.
Follow the model of the XFS trace points and pass in an explіcit offset and length. This has the additional benefit that these values can be more accurate as some of the users touch partial folio ranges.
From the CVE record · Linux
NFS trace events can use nfs_folio_length without the folio lock or a check for a NULL mapping during truncation, potentially crashing the kernel. This can occur with NFS trace points enabled, as observed while running xfstests generic/065. The input does not establish whether authentication, network access, or user interaction is required.
Engineers running Linux kernels with NFS tracing should check their versions; affected versions are not specified.