ext4: fix kernel BUG in ext4_write_inline_data_end
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb · < ad09aa45965d3fafaf9963bc78109b73c0f9ac8d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: fix kernel BUG in ext4_write_inline_data_end
When the data=journal mount option is used, the ext4_journalled_write_end() function incorrectly calls ext4_write_inline_data_end() without checking if the EXT4_STATE_MAY_INLINE_DATA flag is still set on the inode.
If a previous attempt to convert the inline data to an extent failed (e.g. due to ENOSPC), the EXT4_STATE_MAY_INLINE_DATA flag is cleared, but the EXT4_INODE_INLINE_DATA flag remains set. In this scenario, the next call to ext4_write_begin() will not prepare the inline data xattr for writing, but ext4_journalled_write_end() will incorrectly attempt to write to it, triggering a BUG_ON(pos + len > EXT4_I(inode)->i_inline_size) in ext4_write_inline_data() since i_inline_size was not expanded.
Fix this by ensuring that ext4_journalled_write_end() only calls ext4_write_inline_data_end() if the EXT4_STATE_MAY_INLINE_DATA flag is set, mirroring the behavior of ext4_write_end() and ext4_da_write_end().
From the CVE record · Linux
The Linux kernel’s ext4 journalled-write path can mishandle inline data when a filesystem uses the data=journal mount option. If an earlier conversion from inline data to an extent fails, a subsequent write can trigger a kernel BUG. The input does not establish whether an attacker can trigger this remotely or what access they would need.
Anyone running the Linux kernel with ext4 filesystems mounted using data=journal should check whether their kernel is affected; no affected versions are specified.