EUVD-2026-76513
GHSA-g65m-jqm9-5xv8
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local filesystem operation requiring write access to ext2 IS_SYNC inode; no confidentiality impact; integrity loss is high (silent data loss), availability impact is low.
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
Lifecycle Timeline
6DescriptionCVE.org
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().
AnalysisAI
Silent inode metadata loss in the Linux kernel ext2 filesystem affects all systems using ext2 with IS_SYNC inodes: calls to sync_inode_metadata() in ext2_setsize() and ext2_xattr_set2() were guarded by an IS_SYNC branch that skipped mark_inode_dirty(), meaning that if the inode was not already dirty, the sync was a no-op and metadata changes were silently discarded. Affected operations include file truncation and extended attribute writes on synchronous ext2 mounts. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires: (1) an ext2 filesystem must be present and mounted with synchronous write semantics, either via the 'sync' mount option or per-file O_SYNC/IS_SYNC semantics; (2) a process must perform a file truncation (ext2_setsize) or extended attribute write (ext2_xattr_set2) on an inode that is not already marked dirty. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:H = 8.8) is materially overstated and inconsistent with the vulnerability. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Apply the upstream kernel patches at git.kernel.org/stable/c/5efb3350230fef831167740e69e6db2861101186 or git.kernel.org/stable/c/356984d1a5c32e94810cbb6c8dc7d8ff2d4d919a, or upgrade to Linux 7.2.4 or later (7.3-rc1 also contains the fix). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, conduct a comprehensive inventory to identify all systems running ext2 filesystems and their deployment context. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Share
External POC / Exploit Code
Leaving vuln.today