loop: Avoid updating block size under exclusive owner
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 89e4fdecb51cf5535867026274bc97de9480ade5 · < 7e49538288e523427beedd26993d446afef1a6fb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
loop: Avoid updating block size under exclusive owner
Syzbot came up with a reproducer where a loop device block size is changed underneath a mounted filesystem. This causes a mismatch between the block device block size and the block size stored in the superblock causing confusion in various places such as fs/buffer.c. The particular issue triggered by syzbot was a warning in __getblk_slow() due to requested buffer size not matching block device block size.
Fix the problem by getting exclusive hold of the loop device to change its block size. This fails if somebody (such as filesystem) has already an exclusive ownership of the block device and thus prevents modifying the loop device under some exclusive owner which doesn't expect it.
From the CVE record · Linux
A loop device's block size can be changed while a filesystem is mounted on it, causing a mismatch with the filesystem's stored block size. This can cause filesystem confusion and a kernel warning. The input does not specify the access needed to trigger the issue or whether user interaction is required.
Engineers running Linux kernels with loop devices should check their exposure; affected versions are not specified.