ext4: don't set SB_RDONLY after filesystem errors
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 |
|
|
6.6.576.11.46.12In the Linux kernel, the following vulnerability has been resolved:
ext4: don't set SB_RDONLY after filesystem errors
When the filesystem is mounted with errors=remount-ro, we were setting SB_RDONLY flag to stop all filesystem modifications. We knew this misses proper locking (sb->s_umount) and does not go through proper filesystem remount procedure but it has been the way this worked since early ext2 days and it was good enough for catastrophic situation damage mitigation. Recently, syzbot has found a way (see link) to trigger warnings in filesystem freezing because the code got confused by SB_RDONLY changing under its hands. Since these days we set EXT4_FLAGS_SHUTDOWN on the superblock which is enough to stop all filesystem modifications, modifying SB_RDONLY shouldn't be needed. So stop doing that.
From the CVE record · Linux
The Linux kernel’s ext4 code can change the read-only flag after filesystem errors on a filesystem mounted with errors=remount-ro. This can confuse filesystem freezing and trigger warnings. The input does not specify the access, authentication, or user interaction needed to trigger the issue.
Engineers running Linux with ext4 filesystems mounted with errors=remount-ro should check their kernel; affected versions are not specified.