CVE-2026-74308: Linux kernel · ext4: fix kernel BUG in ext4_write_inline_data_end
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f00f5c0dd55319bc33b76f72c853bda0e0a32eda : update Linux kernel when convenient.
Data as of 30 Oct 2026, 13:20 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f00f5c0dd55319bc33b76f72c853bda0e0a32eda, ad09aa45965d3fafaf9963bc78109b73c0f9ac8d, 260830a9a706f5d335398236fc788ce32f220de1 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel source as indicated by multiple fixed commit versions. Users should update their Linux kernel to a version including these fixes to prevent the kernel BUG. No additional mitigation is required beyond applying the official patch.
Description
A kernel bug in the Linux ext4 filesystem was fixed related to the handling of inline data when the data=journal mount option is used. The ext4_journalled_write_end() function could incorrectly call ext4_write_inline_data_end() without verifying a necessary flag, leading to a kernel BUG triggered by an out-of-bounds write attempt. This occurs if a prior conversion of inline data to an extent failed, causing inconsistent inode flags. The fix ensures the function only proceeds if the appropriate flag is set, preventing the kernel BUG.
References
- git.kernel.org/stable/c/13db1ccae4d38f6d9296ee74aa1d39b429959ddb (opens in a new tab)
- git.kernel.org/stable/c/260830a9a706f5d335398236fc788ce32f220de1 (opens in a new tab)
- git.kernel.org/stable/c/9808ae9fae996afa942bd963a39c9b1cdeebd0bd (opens in a new tab)
- git.kernel.org/stable/c/f00f5c0dd55319bc33b76f72c853bda0e0a32eda (opens in a new tab)
- git.kernel.org/stable/c/0ae42b51607240990614e0843f0d3529aaff62cc (opens in a new tab)
- git.kernel.org/stable/c/ad09aa45965d3fafaf9963bc78109b73c0f9ac8d (opens in a new tab)