CVE-2026-89601: Linux kernel · ext2: Fix lost inode updates for IS_SYNC inodes
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in e54de654423bee98d1ba50379b09daf97c7854a6 : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e54de654423bee98d1ba50379b09daf97c7854a6, b879565effd88fc119c2efea3f3868a9997ed9ba, 5481766125041e71662f2e32ee0e91ad5f4d07f4 +2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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().
References
- git.kernel.org/stable/c/b879565effd88fc119c2efea3f3868a9997ed9ba (opens in a new tab)
- git.kernel.org/stable/c/e54de654423bee98d1ba50379b09daf97c7854a6 (opens in a new tab)
- git.kernel.org/stable/c/5481766125041e71662f2e32ee0e91ad5f4d07f4 (opens in a new tab)
- git.kernel.org/stable/c/5efb3350230fef831167740e69e6db2861101186 (opens in a new tab)
- git.kernel.org/stable/c/356984d1a5c32e94810cbb6c8dc7d8ff2d4d919a (opens in a new tab)