CVE-2026-99607

critical

Description

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.

References

https://git.kernel.org/stable/c/6a5200c0f46ab94d0c29ff9934c81d0de6f7b47a

https://git.kernel.org/stable/c/4f91b042af212ca0b610e43f9a975ddc7f0d0923

https://git.kernel.org/stable/c/45d79b40621212ae720d3712d36f31eb3ea1a2d5

https://git.kernel.org/stable/c/2e114662c376f5a5342f2f997c459971dbdf836b

https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-131057

Details

Source: Mitre, NVD

Published: 2026-11-20

Updated: 2026-11-20

Risk Information

CVSS v2

Base Score: 7.5

Vector: CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:P

Severity: High

CVSS v3

Base Score: 9.8

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Severity: Critical

EPSS

EPSS: 0.00168