ext4: don't BUG if someone dirty pages without asking ext4 first
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a42afc5f56f319107e987aa6adf2f65d93d527c7 · < a0856764dc1276ad2dc7891288c2e9246bf11a37| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: don't BUG if someone dirty pages without asking ext4 first
[un]pin_user_pages_remote is dirtying pages without properly warning the file system in advance. A related race was noted by Jan Kara in 2018[1]; however, more recently instead of it being a very hard-to-hit race, it could be reliably triggered by process_vm_writev(2) which was discovered by Syzbot[2].
This is technically a bug in mm/gup.c, but arguably ext4 is fragile in that if some other kernel subsystem dirty pages without properly notifying the file system using page_mkwrite(), ext4 will BUG, while other file systems will not BUG (although data will still be lost).
So instead of crashing with a BUG, issue a warning (since there may be potential data loss) and just mark the page as clean to avoid unprivileged denial of service attacks until the problem can be properly fixed. More discussion and background can be found in the thread starting at [2].
[1] https://lore.kernel.org/linux-mm/20180103100430.GE4911@quack2.suse.cz [2] https://lore.kernel.org/r/Yg0m6IjcNmfaSokM@google.com
From the CVE record · Linux
The Linux kernel's ext4 filesystem can trigger a BUG when another kernel subsystem dirties pages without first notifying ext4. An unprivileged local attacker can reliably trigger this behavior through process_vm_writev(2), causing a denial of service; no user interaction is described.
Operators running Linux kernels with ext4 should check whether their kernel includes the fix; affected versions are not specified.