ext4: skip extra isize expansion during mount to prevent deadlock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c8585c6fcaf2011de54c3592e80a634a2b9e1a7f · < 7ace189b9ea79cf78df9c32b940ce12735f9459a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: skip extra isize expansion during mount to prevent deadlock
ext4_try_to_expand_extra_isize() is called from __ext4_mark_inode_dirty() while holding an active jbd2 handle. During mount (!SB_ACTIVE), the expand path may move xattrs to external blocks and release ea_inodes via iput(). When !SB_ACTIVE, iput() calls write_inode_now() which acquires s_writepages_rwsem, creating a circular lock dependency:
s_writepages_rwsem --> jbd2_handle --> xattr_sem --> s_writepages_rwsem
This can be triggered via:
ext4_process_orphan() -> ext4_truncate() -> ext4_mark_inode_dirty() -> ext4_try_to_expand_extra_isize()
or:
ext4_evict_inode() -> ext4_mark_inode_dirty() -> ext4_try_to_expand_extra_isize()
From the CVE record · Linux
The Linux kernel’s ext4 filesystem can deadlock during mount when inode updates attempt extra-isize expansion. The input does not establish how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running Linux systems that mount ext4 filesystems should check their kernel versions; affected versions are not specified.