ext2: Fix lost inode updates for IS_SYNC inodes
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.114, 6.18.57, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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().
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in b879565effd88fc119c2efea3f3868a9997ed9ba; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in e54de654423bee98d1ba50379b09daf97c7854a6; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5481766125041e71662f2e32ee0e91ad5f4d07f4; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5efb3350230fef831167740e69e6db2861101186; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 356984d1a5c32e94810cbb6c8dc7d8ff2d4d919a
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.4