Skip to content
OpenAdvisories
Unscored CVE-2026-99607 EUVD-2026-131057GHSA-mqmm-53hc-5jpp

ext2: preserve IOMAP_F_DIRTY for extending direct writes

Published Nov 20, 2026 · Assigned by Linux

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.

Affected products

VendorProductAffectedFixed
Linux Linux 6.5 6.12.118

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 linux No fix yet —
Debian 13 linux No fix yet —

Advisories 1

References