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-42295nilfs2: handle inconsistent state in nilfs_btnode_create_block()

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: handle inconsistent state in nilfs_btnode_create_block() Syzbot reported that a buffer state inconsistency was detected in nilfs_btnode_create_block(), triggering a kernel bug. It is not appropriate to treat this inconsistency as a bug; it can occur if the argument block address (the buffer index of the newly created block) is a virtual block number and has been reallocated due to corruption of the bitmap used to manage its allocation state. So, modify nilfs_btnode_create_block() and its callers to treat it as a possible filesystem error, rather than triggering a kernel bug.

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 21 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

CVSS scores of CVE-2024-42295, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (15 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 a60be987d45dd510aeb54389526f9957cfab106c – < 19cce46238ffe3546e44b9c74057103ff8b24c62
    • affected a60be987d45dd510aeb54389526f9957cfab106c – < 02b87e6334a38c65eef49848d3f1ac422f0b2a44
    • affected a60be987d45dd510aeb54389526f9957cfab106c – < 5f0a6800b8aec1b453c7fe4c44fcaac5ffe9d52e
    • affected a60be987d45dd510aeb54389526f9957cfab106c – < e34191cce3ee63dfa5fb241904aaf2a042d5b6d8
    • affected a60be987d45dd510aeb54389526f9957cfab106c – < 012be828a118bf496e666ef1fc47fc0e7358ada2
    • affected a60be987d45dd510aeb54389526f9957cfab106c – < be56dfc9be0604291267c07b0e27a69a6bda4899
    • affected a60be987d45dd510aeb54389526f9957cfab106c – < 366c3f688dd0288cbe38af1d3a886b5c62372e4a
    • affected a60be987d45dd510aeb54389526f9957cfab106c – < 4811f7af6090e8f5a398fbdd766f903ef6c0d787
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 4.19.320 – ≤ 4.19.*
    • unaffected 5.4.282 – ≤ 5.4.*
    • unaffected 5.10.224 – ≤ 5.10.*
    • unaffected 5.15.165 – ≤ 5.15.*
    • unaffected 6.1.103 – ≤ 6.1.*
    • unaffected 6.6.44 – ≤ 6.6.*
    • unaffected 6.10.3 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .