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… (CVE-2026-74308)
A vulnerability in the Linux kernel's ext4 filesystem was resolved that could cause a kernel BUG when using the data=journal mount option. The issue arises because ext4_journalled_write_end() calls ext4_write_inline_data_end() without verifying if the EXT4_STATE_MAY_INLINE_DATA flag is still set on the inode. This can lead to an out-of-bounds write attempt if a previous inline data conversion failed, triggering a kernel BUG. The fix ensures the function only calls ext4_write_inline_data_end() when the flag is set, preventing the erroneous write.
AI Analysis
Technical Summary
The Linux kernel ext4 filesystem had a vulnerability where, under the data=journal mount option, ext4_journalled_write_end() would call ext4_write_inline_data_end() without checking the EXT4_STATE_MAY_INLINE_DATA flag. If a prior attempt to convert inline data to an extent failed (e.g., due to ENOSPC), the flag EXT4_STATE_MAY_INLINE_DATA would be cleared but EXT4_INODE_INLINE_DATA would remain set. This mismatch caused ext4_write_inline_data() to attempt writing beyond the inline data size, triggering a kernel BUG. The patch fixes this by adding a check to ensure ext4_write_inline_data_end() is only called if the EXT4_STATE_MAY_INLINE_DATA flag is set, aligning with the behavior of related functions.
Potential Impact
This vulnerability can cause a kernel BUG, which typically results in a kernel panic or system crash. Such crashes can lead to denial of service conditions on affected systems. There is no information about code execution or privilege escalation impacts. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch to resolve the issue. Since this is a kernel-level bug fix, upgrading to the fixed kernel version is the recommended mitigation. Patch status is not explicitly confirmed in the provided data; users should consult their Linux distribution or kernel vendor advisories for the exact fixed versions and update instructions.
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… (CVE-2026-74308)
Description
A vulnerability in the Linux kernel's ext4 filesystem was resolved that could cause a kernel BUG when using the data=journal mount option. The issue arises because ext4_journalled_write_end() calls ext4_write_inline_data_end() without verifying if the EXT4_STATE_MAY_INLINE_DATA flag is still set on the inode. This can lead to an out-of-bounds write attempt if a previous inline data conversion failed, triggering a kernel BUG. The fix ensures the function only calls ext4_write_inline_data_end() when the flag is set, preventing the erroneous write.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel ext4 filesystem had a vulnerability where, under the data=journal mount option, ext4_journalled_write_end() would call ext4_write_inline_data_end() without checking the EXT4_STATE_MAY_INLINE_DATA flag. If a prior attempt to convert inline data to an extent failed (e.g., due to ENOSPC), the flag EXT4_STATE_MAY_INLINE_DATA would be cleared but EXT4_INODE_INLINE_DATA would remain set. This mismatch caused ext4_write_inline_data() to attempt writing beyond the inline data size, triggering a kernel BUG. The patch fixes this by adding a check to ensure ext4_write_inline_data_end() is only called if the EXT4_STATE_MAY_INLINE_DATA flag is set, aligning with the behavior of related functions.
Potential Impact
This vulnerability can cause a kernel BUG, which typically results in a kernel panic or system crash. Such crashes can lead to denial of service conditions on affected systems. There is no information about code execution or privilege escalation impacts. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch to resolve the issue. Since this is a kernel-level bug fix, upgrading to the fixed kernel version is the recommended mitigation. Patch status is not explicitly confirmed in the provided data; users should consult their Linux distribution or kernel vendor advisories for the exact fixed versions and update instructions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-grvr-g5pp-pc9x
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74308"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a808b6bbf8831d5394f729a
Added to database: 08/15/2026, 15:53:15 UTC
Last enriched: 08/15/2026, 16:10:32 UTC
Last updated: 08/15/2026, 16:10:32 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.