ext2: Fix lost inode updates for IS_SYNC inodes
CVE-2026-89601 · published 11 Sept 2026
How serious is it
- Severity: high, CVSS score 8.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-89601?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < b879565effd88fc119c2efea3f3868a9997ed9ba, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < e54de654423bee98d1ba50379b09daf97c7854a6, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 5481766125041e71662f2e32ee0e91ad5f4d07f4, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 5efb3350230fef831167740e69e6db2861101186
- Linux Linux: 2.6.12
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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().
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/b879565effd88fc119c2efea3f3868a9997ed9ba
- git.kernel.org/stable/c/e54de654423bee98d1ba50379b09daf97c7854a6
- git.kernel.org/stable/c/5481766125041e71662f2e32ee0e91ad5f4d07f4
- git.kernel.org/stable/c/5efb3350230fef831167740e69e6db2861101186
- git.kernel.org/stable/c/356984d1a5c32e94810cbb6c8dc7d8ff2d4d919a
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON