CVE-2026-74307ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a before 74796e886ca39fcb0d3fd36ea6a39c62784ab6fb; from fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a before 29e07ec352f0ad06c833a18bf47d82c81f55544f; from fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a before fb52013cad9e9b7d3a6a14ea1bcd841e41da7c6c; from fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a before c143957520c6c9b5cd72e0de8b52b814f0c576fe | CNA record |
References
- https://git.kernel.org/stable/c/74796e886ca39fcb0d3fd36ea6a39c62784ab6fb
- https://git.kernel.org/stable/c/29e07ec352f0ad06c833a18bf47d82c81f55544f
- https://git.kernel.org/stable/c/fb52013cad9e9b7d3a6a14ea1bcd841e41da7c6c
- https://git.kernel.org/stable/c/c143957520c6c9b5cd72e0de8b52b814f0c576fe
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.