Answer in brief
CVE-2026-74308 records a Unknown severity vulnerability in ext4: fix kernel BUG in ext4_write_inline_data_end. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb <260830a9a706f5d335398236fc788ce32f220de1 || >=3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb <9808ae9fae996afa942bd963a39c9b1cdeebd0bd || >=3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb <f00f5c0dd55319bc33b76f72c853bda0e0a32eda || >=3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb <0ae42b51607240990614e0843f0d3529aaff62cc || >=3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb <ad09aa45965d3fafaf9963bc78109b73c0f9ac8d | 260830a9a706f5d335398236fc788ce32f220de1, 9808ae9fae996afa942bd963a39c9b1cdeebd0bd, f00f5c0dd55319bc33b76f72c853bda0e0a32eda, 0ae42b51607240990614e0843f0d3529aaff62cc, ad09aa45965d3fafaf9963bc78109b73c0f9ac8d |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74308 records a Unknown severity vulnerability in ext4: fix kernel BUG in ext4_write_inline_data_end. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb <260830a9a706f5d335398236fc788ce32f220de1 || >=3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb <9808ae9fae996afa942bd963a39c9b1cdeebd0bd || >=3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb <f00f5c0dd55319bc33b76f72c853bda0e0a32eda || >=3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb <0ae42b51607240990614e0843f0d3529aaff62cc || >=3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb <ad09aa45965d3fafaf9963bc78109b73c0f9ac8d | 260830a9a706f5d335398236fc788ce32f220de1, 9808ae9fae996afa942bd963a39c9b1cdeebd0bd, f00f5c0dd55319bc33b76f72c853bda0e0a32eda, 0ae42b51607240990614e0843f0d3529aaff62cc, ad09aa45965d3fafaf9963bc78109b73c0f9ac8d |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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().
Quoted source text, attributed separately from HOL analysis.