https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 02:04:45 +0000 https://vulnerability.circl.lu/vuln/cve-2026-89601 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ext2: Fix lost inode updates for IS_SYNC inodes</p> <p>ext2_setsize() and ext2_xattr_set2() had a construct like:</p> <p>if (IS_SYNC(inode)) { sync_inode_metadata(inode, 1); } else { mark_inode_dirty(inode); }</p> <p>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().</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ext2: Fix lost inode updates for IS_SYNC inodes</p> <p>ext2_setsize() and ext2_xattr_set2() had a construct like:</p> <p>if (IS_SYNC(inode)) { sync_inode_metadata(inode, 1); } else { mark_inode_dirty(inode); }</p> <p>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().</p> https://vulnerability.circl.lu/vuln/cve-2026-89601