Description
In 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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
95257987a6387f02970eda707e55a06cce734e18 to < 58c0648e4c773f5b54f0cb63bc8c7c6bf52719a9affected95257987a6387f02970eda707e55a06cce734e18 to < ee77c388469116565e009eaa704a60bc78489e09affected95257987a6387f02970eda707e55a06cce734e18 to < d3476f3dad4ad68ae5f6b008ea6591d1520da5d8affected
Linux Linux
Default version status: affected
6.6affected0 to < 6.6unaffected6.6.57 to ≤ 6.6.*unaffected6.11.4 to ≤ 6.11.*unaffected6.12 to ≤ *unaffected