CVE Catalog

CVE-2026-89601

HighCVSS 8.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.35%

28th percentile - higher than 28% of all known CVEs

Summary

In the Linux kernel, ext2_setsize() and ext2_xattr_set2() contained a construct that for IS_SYNC inodes called sync_inode_metadata() instead of marking the inode dirty. Since sync_inode_metadata() only acts if the inode is already dirty, inode updates could be lost.

Risk Assessment

Lost inode updates may lead to data inconsistency and potential data loss in ext2 filesystems. The risk affects systems using ext2 with IS_SYNC inodes.

Recommendation

Update the Linux kernel to a version containing the fix that unconditionally marks the inode dirty and then calls sync_inode_metadata(). Avoid using ext2 with IS_SYNC inodes until the fix is applied, if possible.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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().

Vulnerability data from NVD (NIST) · CISA KEV · EPSS