CVE-2024-50191
Published Nov 8, 2024
Last updated 9 days ago
Overview
- 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.
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- NVD status
- Awaiting Analysis
Social media
- Hype score
- Not currently trending
CVE-2024-50191 Linux Kernel FIX ext4 SB_RDONLY Missteps Corrected After Filesystem Errors: In the Linux kernel, a vulnerability has been fixed: ext4: don't change SB_RDONLY after filesystem errors Previously, w... https://t.co/ZVwBRscGeW
@VulmonFeeds
8 Nov 2024
19 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
CVE-2024-50191 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=rem… https://t.co/xxOCfhfNMk
@CVEnew
8 Nov 2024
250 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes