CVE-2026-99607
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/2e114662c376f5a5342f2f997c459971dbdf836b
- git.kernel.org/stable/c/45d79b40621212ae720d3712d36f31eb3ea1a2d5
- git.kernel.org/stable/c/4f91b042af212ca0b610e43f9a975ddc7f0d0923
- git.kernel.org/stable/c/6a5200c0f46ab94d0c29ff9934c81d0de6f7b47a
- nvd.nist.gov/vuln/detail/CVE-2026-99607
- cve.org/CVERecord?id=CVE-2026-99607
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.