ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fb52013cad9e9b7d3a6a14ea1bcd841e41da7c6c, Kernel 23380fc1bf5d3b75dcbd51eb72be4eb0a3300370, Kernel 29e07ec352f0ad06c833a18bf47d82c81f55544f and 8 more.
In the Linux kernel, the following vulnerability has been resolved: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT Reject the EXT4_IOC_MOVE_EXT ioctl early if the donor file does not belong to the same superblock as the original file. Currently, this validation is performed inside ext4_move_extents() by mext_check_validity(), but only after lock_two_nondirectories() has already acquired the inode locks. When the donor fd refers to a file on a different filesystem (e.g., overlayfs), this late validation creates a circular lock dependency: CPU0 (overlayfs write) CPU1 (ext4 ioctl) ---- ---- inode_lock(ovl_inode) mnt_want_write_file(filp) sb_start_write(ext4_sb) [sb_writers] backing_file_write_iter() vfs_iter_write(real_file) file_start_write(real_file) sb_start_write(ext4_sb) [blocked by freeze] lock_two_nondirectories() inode_lock(ovl_inode) [blocked] With a concurrent freeze operation holding sb_writers write side, this forms a deadlock cycle: CPU0 waits for freeze to complete, freeze waits for CPU1's sb_writers reader to exit, CPU1 waits for CPU0's inode lock. Since EXT4_IOC_MOVE_EXT exchanges physical extents between two files, it fundamentally requires both files to reside on the same ext4 filesystem. Moving the superblock check before any lock acquisition is both semantically correct and eliminates the circular dependency by ensuring that cross-filesystem donor fds are rejected before sb_writers or inode locks are taken.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <fb52013cad9e9b7d3a6a14ea1bcd841e41da7c6c, >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <23380fc1bf5d3b75dcbd51eb72be4eb0a3300370, >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <29e07ec352f0ad06c833a18bf47d82c81f55544f, >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <663f184b51492093d408e518efc95ee13b5b4440, >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <74796e886ca39fcb0d3fd36ea6a39c62784ab6fb, >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <c143957520c6c9b5cd72e0de8b52b814f0c576fe, =3.18 | fb52013cad9e9b7d3a6a14ea1bcd841e41da7c6c, 23380fc1bf5d3b75dcbd51eb72be4eb0a3300370, 29e07ec352f0ad06c833a18bf47d82c81f55544f, 663f184b51492093d408e518efc95ee13b5b4440, 74796e886ca39fcb0d3fd36ea6a39c62784ab6fb, c143957520c6c9b5cd72e0de8b52b814f0c576fe |
| linux-kernel: Kernel | >=6.13.0 <6.18.57, >=6.19.0 <7.1.5, >=6.2.0 <6.6.160, >=6.7.0 <6.12.97, >=3.18.0 <6.1.191 | 6.18.57, 7.1.5, 6.6.160, 6.12.97, 6.1.191 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket