ext2: Fix lost inode updates for IS_SYNC inodes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 356984d1a5c32e94810cbb6c8dc7d8ff2d4d919a| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel's ext2 code can lose updates to IS_SYNC inodes when it attempts to synchronize metadata before marking the inode dirty. The input does not describe how an attacker could trigger this issue or specify network access, authentication, or user interaction requirements.
Engineers running the Linux kernel with ext2 should check their deployments; affected versions are not specified.