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-53130nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint When using the "block:block_dirty_buffer" tracepoint, mark_buffer_dirty() may cause a NULL pointer dereference, or a general protection fault when KASAN is enabled. This happens because, since the tracepoint was added in mark_buffer_dirty(), it references the dev_t member bh->b_bdev->bd_dev regardless of whether the buffer head has a pointer to a block_device structure. In the current implementation, nilfs_grab_buffer(), which grabs a buffer to read (or create) a block of metadata, including b-tree node blocks, does not set the block device, but instead does so only if the buffer is not in the "uptodate" state for each of its caller block reading functions. However, if the uptodate flag is set on a folio/page, and the buffer heads are detached from it by try_to_free_buffers(), and new buffer heads are then attached by create_empty_buffers(), the uptodate flag may be restored to each buffer without the block device being set to bh->b_bdev, and mark_buffer_dirty() may be called later in that state, resulting in the bug mentioned above. Fix this issue by making nilfs_grab_buffer() always set the block device of the super block structure to the buffer head, regardless of the state of the buffer's uptodate flag.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 17 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-53130, 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.24% · top 85% of all CVEs (18 Nov 2026)
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 5305cb830834549b9203ad4d009ad5483c5e293f – < 7af3309c7a2ef26831a67125b11c34a7e01c1b2a
    • affected 5305cb830834549b9203ad4d009ad5483c5e293f – < 0ce59fb1c73fdd5b6028226aeb46259a0cdc0957
    • affected 5305cb830834549b9203ad4d009ad5483c5e293f – < 0a5014ad37c77ac6a2c525137c00a0e1724f6020
    • affected 5305cb830834549b9203ad4d009ad5483c5e293f – < d904e4d845aafbcfd8a40c1df7d999f02f062be8
    • affected 5305cb830834549b9203ad4d009ad5483c5e293f – < 86b19031dbc79abc378dfae357f6ea33ebeb0c95
    • affected 5305cb830834549b9203ad4d009ad5483c5e293f – < b0e4765740040c44039282057ecacd7435d1d2ba
    • affected 5305cb830834549b9203ad4d009ad5483c5e293f – < ffc440a76a0f476a7e6ea838ec0dc8e9979944d1
    • affected 5305cb830834549b9203ad4d009ad5483c5e293f – < 2026559a6c4ce34db117d2db8f710fe2a9420d5a
  • Linux · Linux

    • affected 3.9
    • unaffected < 3.9
    • unaffected 4.19.325 – ≤ 4.19.*
    • unaffected 5.4.287 – ≤ 5.4.*
    • unaffected 5.10.231 – ≤ 5.10.*
    • unaffected 5.15.174 – ≤ 5.15.*
    • unaffected 6.1.119 – ≤ 6.1.*
    • unaffected 6.6.63 – ≤ 6.6.*
    • unaffected 6.11.10 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .