UNKNOWNCVSS not yet scoredVulnerability

CVE-2026-99607

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.

Properties

Last source
FIRST EPSS
Nvd fetched at
2026-11-22T12:30:49.958423+00:00
Epss score
0.00168
Cve id
CVE-2026-99607
First seen by Signal
2026-11-20T07:38:10+00:00
Name
CVE-2026-99607
Retrieved at
2026-11-22T12:32:29+00:00
Published at
2026-11-20T06:17:52.867
Last modified
2026-11-20T06:17:52.867
Epss percentile
0.06185

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-99607 — Ninja Signal Threat Intelligence | Ninja Signal