smb: client: discard post-EOF pagecache when extending a file via zero range
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 72c419d9b073628d3b5b0b2fc787b724f1a8c726 · < 6a8279c98ad289b27c0bdb11adb3f0c0b7fd456d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
smb: client: discard post-EOF pagecache when extending a file via zero range
smb3_zero_range() removed the pagecache only for the range being zeroed, so when it extends the file the folio straddling the old EOF - which may hold data dirtied past EOF through an mmap - was never dropped and became visible as file content once the file was extended.
Lower the discard boundary to the smaller of the zero-range offset and the old EOF.
From the CVE record · Linux
The Linux kernel SMB client may expose data dirtied past a file’s end through mmap when a zero-range operation extends the file. The input does not specify how an attacker could trigger this, whether authentication is required, or whether user interaction is needed.
Engineers running the Linux kernel should check whether their version includes the affected SMB client code; affected versions are not specified.