Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74308ext4: fix kernel BUG in ext4_write_inline_data_end

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb – < 13db1ccae4d38f6d9296ee74aa1d39b429959ddb
    • affected 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb – < 260830a9a706f5d335398236fc788ce32f220de1
    • affected 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb – < 9808ae9fae996afa942bd963a39c9b1cdeebd0bd
    • affected 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb – < f00f5c0dd55319bc33b76f72c853bda0e0a32eda
    • affected 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb – < 0ae42b51607240990614e0843f0d3529aaff62cc
    • affected 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb – < ad09aa45965d3fafaf9963bc78109b73c0f9ac8d
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74308 badge
[![CVE-2026-74308](https://cveledger.app/badge/CVE-2026-74308.svg)](https://cveledger.app/cve/CVE-2026-74308)

Record last updated .