File-size persistence failure via cleared dirty flag
Published Nov 20, 2026 · Updated Nov 20, 2026
Linux ext2 durability failure allows local users to complete synchronous direct writes without persisting the enlarged file size. ext2_iomap_begin() clears IOMAP_F_DIRTY after ext2_get_blocks(), allowing iomap to skip generic_write_sync() despite an inode-size update. The documented case requires write access to an ext2 file, an existing mapped block, and a FUA-capable device; an O_DIRECT|O_DSYNC extension succeeds while the on-disk inode retains its old size.
Summary
What happened
Linux ext2 durability failure allows local users to complete synchronous direct writes without persisting the enlarged file size. ext2_iomap_begin() clears IOMAP_F_DIRTY after ext2_get_blocks(), allowing iomap to skip generic_write_sync() despite an inode-size update. The documented case requires write access to an ext2 file, an existing mapped block, and a FUA-capable device; an O_DIRECT|O_DSYNC extension succeeds while the on-disk inode retains its old size.
The record
- CVE
- CVE-2026-99607
- Published
- Nov 20, 2026
- Updated
- Nov 20, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 20, 2026CVE publishedPublication date reported by the CVE source.
- Nov 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.5
- Affected versionversion=fb5de4358e1aa4753dce73c4dc1aca73ff39cedd <2e114662c376f5a5342f2f997c459971dbdf836b
- Affected versionversion=fb5de4358e1aa4753dce73c4dc1aca73ff39cedd <45d79b40621212ae720d3712d36f31eb3ea1a2d5
- Affected versionversion=fb5de4358e1aa4753dce73c4dc1aca73ff39cedd <4f91b042af212ca0b610e43f9a975ddc7f0d0923
- Affected versionversion=fb5de4358e1aa4753dce73c4dc1aca73ff39cedd <6a5200c0f46ab94d0c29ff9934c81d0de6f7b47a
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us