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-2024-26956nilfs2: fix failure to detect DAT corruption in btree and direct mappings

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix failure to detect DAT corruption in btree and direct mappings Patch series "nilfs2: fix kernel bug at submit_bh_wbc()". This resolves a kernel BUG reported by syzbot. Since there are two flaws involved, I've made each one a separate patch. The first patch alone resolves the syzbot-reported bug, but I think both fixes should be sent to stable, so I've tagged them as such. This patch (of 2): Syzbot has reported a kernel bug in submit_bh_wbc() when writing file data to a nilfs2 file system whose metadata is corrupted. There are two flaws involved in this issue. The first flaw is that when nilfs_get_block() locates a data block using btree or direct mapping, if the disk address translation routine nilfs_dat_translate() fails with internal code -ENOENT due to DAT metadata corruption, it can be passed back to nilfs_get_block(). This causes nilfs_get_block() to misidentify an existing block as non-existent, causing both data block lookup and insertion to fail inconsistently. The second flaw is that nilfs_get_block() returns a successful status in this inconsistent state. This causes the caller __block_write_begin_int() or others to request a read even though the buffer is not mapped, resulting in a BUG_ON check for the BH_Mapped flag in submit_bh_wbc() failing. This fixes the first issue by changing the return value to code -EINVAL when a conversion using DAT fails with code -ENOENT, avoiding the conflicting condition that leads to the kernel bug described above. Here, code -EINVAL indicates that metadata corruption was detected during the block lookup, which will be properly handled as a file system error and converted to -EIO when passing through the nilfs2 bmap layer.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 2 years 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

CVSS scores of CVE-2024-26956, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.26% · top 83% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected c3a7abf06ce719a51139e62a034590be99abbc2c – < b67189690eb4b7ecc84ae16fa1e880e0123eaa35
    • affected c3a7abf06ce719a51139e62a034590be99abbc2c – < 9cbe1ad5f4354f4df1445e5f4883983328cd6d8e
    • affected c3a7abf06ce719a51139e62a034590be99abbc2c – < c3b5c5c31e723b568f83d8cafab8629d9d830ffb
    • affected c3a7abf06ce719a51139e62a034590be99abbc2c – < 2e2619ff5d0def4bb6c2037a32a6eaa28dd95c84
    • affected c3a7abf06ce719a51139e62a034590be99abbc2c – < 46b832e09d43b394ac0f6d9485d2b1a06593f0b7
    • affected c3a7abf06ce719a51139e62a034590be99abbc2c – < f69e81396aea66304d214f175aa371f1b5578862
    • affected c3a7abf06ce719a51139e62a034590be99abbc2c – < a8e4d098de1c0f4c5c1f2ed4633a860f0da6d713
    • affected c3a7abf06ce719a51139e62a034590be99abbc2c – < 82827ca21e7c8a91384c5baa656f78a5adfa4ab4
    • affected c3a7abf06ce719a51139e62a034590be99abbc2c – < f2f26b4a84a0ef41791bd2d70861c8eac748f4ba
  • Linux · Linux

    • affected 2.6.31
    • unaffected < 2.6.31
    • unaffected 4.19.312 – ≤ 4.19.*
    • unaffected 5.4.274 – ≤ 5.4.*
    • unaffected 5.10.215 – ≤ 5.10.*
    • unaffected 5.15.154 – ≤ 5.15.*
    • unaffected 6.1.84 – ≤ 6.1.*
    • unaffected 6.6.24 – ≤ 6.6.*
    • unaffected 6.7.12 – ≤ 6.7.*
    • unaffected 6.8.3 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .