PT-2026-152487
CVE-2026-99607
·
Published
2026-11-20
·
Updated
2026-11-20
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾