ext2: Fix lost inode updates for IS_SYNC inodes
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 356984d1a5c32e94810cbb6c8dc7d8ff2d4d919a, Kernel 5481766125041e71662f2e32ee0e91ad5f4d07f4, Kernel 55e66d84b5272c425b324a2b247cdacacf1e10b9 and 3 more.
In the Linux kernel, the following vulnerability has been resolved: ext2: Fix lost inode updates for IS_SYNC inodes ext2_setsize() and ext2_xattr_set2() had a construct like: if (IS_SYNC(inode)) { sync_inode_metadata(inode, 1); } else { mark_inode_dirty(inode); } which leads to lost inode updates for IS_SYNC inodes because sync_inode_metadata() does anything only if the inode is already dirty and hence inode updates may be simply lost. Fix the problem by unconditionally marking the inode dirty and *then* call sync_inode_metadata().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.12, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <356984d1a5c32e94810cbb6c8dc7d8ff2d4d919a, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5481766125041e71662f2e32ee0e91ad5f4d07f4, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <55e66d84b5272c425b324a2b247cdacacf1e10b9, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5efb3350230fef831167740e69e6db2861101186, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b879565effd88fc119c2efea3f3868a9997ed9ba, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e54de654423bee98d1ba50379b09daf97c7854a6 | 356984d1a5c32e94810cbb6c8dc7d8ff2d4d919a, 5481766125041e71662f2e32ee0e91ad5f4d07f4, 55e66d84b5272c425b324a2b247cdacacf1e10b9, 5efb3350230fef831167740e69e6db2861101186, b879565effd88fc119c2efea3f3868a9997ed9ba, e54de654423bee98d1ba50379b09daf97c7854a6 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket