CVE-2026-45985 PUBLISHED

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O

Assigner: Linux
Reserved: 13.05.2026 Published: 27.05.2026 Updated: 27.05.2026

In the Linux kernel, the following vulnerability has been resolved:

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O

When allocating blocks during within-EOF DIO and writeback with dioread_nolock enabled, EXT4_GET_BLOCKS_PRE_IO was set to split an existing large unwritten extent. However, EXT4_GET_BLOCKS_CONVERT was set when calling ext4_split_convert_extents(), which may potentially result in stale data issues.

Assume we have an unwritten extent, and then DIO writes the second half.

[UUUUUUUUUUUUUUUU] on-disk extent U: unwritten extent [UUUUUUUUUUUUUUUU] extent status tree |<- ->| ----> dio write this range

First, ext4_iomap_alloc() call ext4_map_blocks() with EXT4_GET_BLOCKS_PRE_IO, EXT4_GET_BLOCKS_UNWRIT_EXT and EXT4_GET_BLOCKS_CREATE flags set. ext4_map_blocks() find this extent and call ext4_split_convert_extents() with EXT4_GET_BLOCKS_CONVERT and the above flags set.

Then, ext4_split_convert_extents() calls ext4_split_extent() with EXT4_EXT_MAY_ZEROOUT, EXT4_EXT_MARK_UNWRIT2 and EXT4_EXT_DATA_VALID2 flags set, and it calls ext4_split_extent_at() to split the second half with EXT4_EXT_DATA_VALID2, EXT4_EXT_MARK_UNWRIT1, EXT4_EXT_MAY_ZEROOUT and EXT4_EXT_MARK_UNWRIT2 flags set. However, ext4_split_extent_at() failed to insert extent since a temporary lack -ENOSPC. It zeroes out the first half but convert the entire on-disk extent to written since the EXT4_EXT_DATA_VALID2 flag set, but left the second half as unwritten in the extent status tree.

[0000000000SSSSSS] data S: stale data, 0: zeroed [WWWWWWWWWWWWWWWW] on-disk extent W: written extent [WWWWWWWWWWUUUUUU] extent status tree

Finally, if the DIO failed to write data to the disk, the stale data in the second half will be exposed once the cached extent entry is gone.

Fix this issue by not passing EXT4_GET_BLOCKS_CONVERT when splitting an unwritten extent before submitting I/O, and make ext4_split_convert_extents() to zero out the entire extent range to zero for this case, and also mark the extent in the extent status tree for consistency.

Product Status

Vendor Linux
Product Linux
Versions Default: unaffected
  • affected from b8a8684502a0fc852afa0056c6bb2a9273f6fcc0 to 77e407967cd872cd75d7e4a691908e49c8e6b4d4 (excl.)
  • affected from b8a8684502a0fc852afa0056c6bb2a9273f6fcc0 to 37555690f39f78ef69af347d9aff897e07445949 (excl.)
  • affected from b8a8684502a0fc852afa0056c6bb2a9273f6fcc0 to 67cdb7bd7442bd3cdc6d6088bbb2df9be2fe936c (excl.)
  • affected from b8a8684502a0fc852afa0056c6bb2a9273f6fcc0 to 2920ec61c98b9476781359f05b94da84e80f54d4 (excl.)
  • affected from b8a8684502a0fc852afa0056c6bb2a9273f6fcc0 to 2698731d25823267c29190cb578da9296a0c0d7b (excl.)
  • affected from b8a8684502a0fc852afa0056c6bb2a9273f6fcc0 to 716e7439a5a9b18c3ff882c2f8c834b9ced1aaec (excl.)
  • affected from b8a8684502a0fc852afa0056c6bb2a9273f6fcc0 to feaf2a80e78f89ee8a3464126077ba8683b62791 (excl.)
Vendor Linux
Product Linux
Versions Default: affected
  • Version 3.15 is affected
  • unaffected from 0 to 3.15 (excl.)
  • unaffected from 5.10.253 to 5.10.* (incl.)
  • unaffected from 5.15.203 to 5.15.* (incl.)
  • unaffected from 6.6.130 to 6.6.* (incl.)
  • unaffected from 6.12.77 to 6.12.* (incl.)
  • unaffected from 6.18.17 to 6.18.* (incl.)
  • unaffected from 6.19.4 to 6.19.* (incl.)
  • unaffected from 7.0 to * (incl.)

References