CVE-2026-74308

ext4: fix kernel BUG in ext4_write_inline_data_end

N/A
Published: August 15, 2026 at 05:58 AM UTC
Updated: August 17, 2026 at 06:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.8 ≤ v < 6.12.973.8 ≤ v < 6.18.403.8 ≤ v < 6.6.1453.8 ≤ v < 7.1.53.8 ≤ v < 7.23.83fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb
Vendor states this is fixed in 0ae42b51607240990614e0843f0d3529aaff62cc (fixed)
Vendor states this is fixed in 260830a9a706f5d335398236fc788ce32f220de1 (fixed)
Vendor states this is fixed in 9808ae9fae996afa942bd963a39c9b1cdeebd0bd (fixed)
Vendor states this is fixed in ad09aa45965d3fafaf9963bc78109b73c0f9ac8d (fixed)
Vendor states this is fixed in f00f5c0dd55319bc33b76f72c853bda0e0a32eda (fixed)
Vendor states this is fixed in 3.8 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card