netfs: Fix potential for tearing in ->remote_i_size and ->zero_point
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfs: Fix potential for tearing in ->remote_i_size and ->zero_point
Fix potential tearing in using ->remote_i_size and ->zero_point by copying i_size_read() and i_size_write() and using the same seqcount as for i_size.
We need to make sure that netfslib and the filesystems that use it always hold i_lock whilst updating any of the sizes to prevent i_size_seqcount from getting corrupted.
From the CVE record · Linux
The Linux kernel’s netfs code could read torn values from remote_i_size and zero_point during concurrent size updates. The input does not specify how an attacker could trigger this issue or whether access or user interaction is required.
Teams running Linux kernels that include netfs should check their kernel’s vendor advisory for affected versions.