Skip to main content
VulnerabilityPublished

CVE-2026-99607: Linux kernel · ext2: preserve IOMAP_F_DIRTY for extending direct writes

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in 45d79b40621212ae720d3712d36f31eb3ea1a2d5 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:19 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 45d79b40621212ae720d3712d36f31eb3ea1a2d5, 6a5200c0f46ab94d0c29ff9934c81d0de6f7b47a, 4f91b042af212ca0b610e43f9a975ddc7f0d0923 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to 45d79b40621212ae720d3712d36f31eb3ea1a2d5, 6a5200c0f46ab94d0c29ff9934c81d0de6f7b47a, 4f91b042af212ca0b610e43f9a975ddc7f0d0923 or 2e114662c376f5a5342f2f997c459971dbdf836b.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ fb5de4358e1aa4753dce73c4dc1aca73ff39cedd, < 45d79b40621212ae720d3712d36f31eb3ea1a2d5
Fixed in
  • 45d79b40621212ae720d3712d36f31eb3ea1a2d5
LinuxLinuxAffected
  • ≥ fb5de4358e1aa4753dce73c4dc1aca73ff39cedd, < 6a5200c0f46ab94d0c29ff9934c81d0de6f7b47a
Fixed in
  • 6a5200c0f46ab94d0c29ff9934c81d0de6f7b47a
LinuxLinuxAffected
  • ≥ fb5de4358e1aa4753dce73c4dc1aca73ff39cedd, < 4f91b042af212ca0b610e43f9a975ddc7f0d0923
Fixed in
  • 4f91b042af212ca0b610e43f9a975ddc7f0d0923
LinuxLinuxAffected
  • ≥ fb5de4358e1aa4753dce73c4dc1aca73ff39cedd, < 2e114662c376f5a5342f2f997c459971dbdf836b
Fixed in
  • 2e114662c376f5a5342f2f997c459971dbdf836b
LinuxLinuxAffected
  • =6.5
Fixed in–

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

Community reviews

Loading reviews…