In the Linux kernel, the following vulnerability has been resolved: ext2: Fix lost inode updates for IS_SYNC inodes ext2_setsize() and… (CVE-2026-89601)
A vulnerability in the Linux kernel's ext2 filesystem code caused lost inode updates for synchronous (IS_SYNC) inodes due to improper handling in ext2_setsize() and ext2_xattr_set2(). The issue was that sync_inode_metadata() only acted if the inode was already marked dirty, leading to updates being lost. The fix involves marking the inode dirty unconditionally before calling sync_inode_metadata().
AI Analysis
Technical Summary
The Linux kernel ext2 filesystem had a flaw where inode updates for IS_SYNC inodes could be lost. The functions ext2_setsize() and ext2_xattr_set2() conditionally called sync_inode_metadata() only if the inode was already dirty, but this condition was not always met, causing updates to be dropped. The patch ensures the inode is marked dirty unconditionally before invoking sync_inode_metadata(), preventing lost updates.
Potential Impact
Lost inode updates for synchronous inodes could result in filesystem metadata inconsistencies or data integrity issues on ext2 filesystems. This could affect system stability or data reliability where ext2 is used with synchronous inode operations.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by changing the inode update logic. Users should apply the official kernel update that includes this patch to resolve the vulnerability.
In the Linux kernel, the following vulnerability has been resolved: ext2: Fix lost inode updates for IS_SYNC inodes ext2_setsize() and… (CVE-2026-89601)
Description
A vulnerability in the Linux kernel's ext2 filesystem code caused lost inode updates for synchronous (IS_SYNC) inodes due to improper handling in ext2_setsize() and ext2_xattr_set2(). The issue was that sync_inode_metadata() only acted if the inode was already marked dirty, leading to updates being lost. The fix involves marking the inode dirty unconditionally before calling sync_inode_metadata().
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel ext2 filesystem had a flaw where inode updates for IS_SYNC inodes could be lost. The functions ext2_setsize() and ext2_xattr_set2() conditionally called sync_inode_metadata() only if the inode was already dirty, but this condition was not always met, causing updates to be dropped. The patch ensures the inode is marked dirty unconditionally before invoking sync_inode_metadata(), preventing lost updates.
Potential Impact
Lost inode updates for synchronous inodes could result in filesystem metadata inconsistencies or data integrity issues on ext2 filesystems. This could affect system stability or data reliability where ext2 is used with synchronous inode operations.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by changing the inode update logic. Users should apply the official kernel update that includes this patch to resolve the vulnerability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-g65m-jqm9-5xv8
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89601"]
Threat ID: 6aa4a00c55bf5e2cf5a86680
Added to database: 09/12/2026, 00:42:52 UTC
Last enriched: 09/12/2026, 01:03:33 UTC
Last updated: 09/12/2026, 01:03:33 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.