smb/client: fix stale page cache in insert/collapse range
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
smb/client: fix stale page cache in insert/collapse range
smb3_insert_range() and smb3_collapse_range() use truncate_pagecache_range() to invalidate the affected page cache. However, if off or old_eof is not page-aligned, the boundary pages are only partially zeroed and remain uptodate. As a result, the client may return stale data after a successful insert/collapse range operation.
For example, with 4K pages:
page 0 page 1 page 2 0------4K 4K------8K 8K------12K ^ ^ off=2K old_eof=10K
Page 1 is removed from the page cache, while the boundary pages are only partially zeroed. After COPYCHUNK moves the data on the server, these cached pages may still return stale data.
This can be reproduced on a CIFS mount:
bash -c ' FILE=/mnt/scratch/repro
From the CVE record · Linux
The Linux kernel SMB client can return stale cached data after an insert-range or collapse-range operation on a CIFS mount. This occurs when the affected offset or previous end-of-file is not page-aligned; the input does not describe an attacker or authentication requirements.
Engineers running the Linux kernel SMB client on CIFS mounts should check their kernel versions; affected versions are not specified.