CVE-2026-99607

published 20 Nov 2026 · updated 20 Nov 2026

ext2: preserve IOMAP_F_DIRTY for extending direct writes

9.8CriticalCVSS 9.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6a5200c0f46ab94d0c29ff9934c81d0de6f7b47a, Kernel 2e114662c376f5a5342f2f997c459971dbdf836b, Kernel 45d79b40621212ae720d3712d36f31eb3ea1a2d5 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: ext2: preserve IOMAP_F_DIRTY for extending direct writes ext2_iomap_begin() sets IOMAP_F_DIRTY for writes that may extend i_size, but clears the flag after ext2_get_blocks(). When the write uses an existing mapped block, iomap can then use FUA and skip generic_write_sync(), even though ext2_dio_write_end_io() updates the inode size. An O_DSYNC write can therefore return without persisting the new size. For example, on a FUA-capable device, a 512-byte O_DIRECT|O_DSYNC write at offset 512 into a fsynced one-byte file returns successfully and extends the in-memory size to 1024, while an immediate read of the on-disk inode still shows size 1. An explicit fsync persists the new size. Move setting of IOMAP_F_DIRTY after the initialization.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=fb5de4358e1aa4753dce73c4dc1aca73ff39cedd <6a5200c0f46ab94d0c29ff9934c81d0de6f7b47a, >=fb5de4358e1aa4753dce73c4dc1aca73ff39cedd <2e114662c376f5a5342f2f997c459971dbdf836b, >=fb5de4358e1aa4753dce73c4dc1aca73ff39cedd <45d79b40621212ae720d3712d36f31eb3ea1a2d5, >=fb5de4358e1aa4753dce73c4dc1aca73ff39cedd <4f91b042af212ca0b610e43f9a975ddc7f0d0923, =6.56a5200c0f46ab94d0c29ff9934c81d0de6f7b47a, 2e114662c376f5a5342f2f997c459971dbdf836b, 45d79b40621212ae720d3712d36f31eb3ea1a2d5, 4f91b042af212ca0b610e43f9a975ddc7f0d0923
linux-kernel: Kernel>=6.19.0 <7.3.5, >=6.5.0 <6.12.118, >=6.13.0 <6.18.647.3.5, 6.12.118, 6.18.64

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99607 severity on Zeptric[![CVE-2026-99607](https://zeptric.io/badge/cve/CVE-2026-99607.svg)](https://zeptric.io/cve/CVE-2026-99607)