Local system crash via unset block-device pointer
Published Dec 4, 2024 · Updated May 11, 2026
NULL pointer dereference in Linux kernel NILFS2 allows local users to crash the system when the block_dirty_buffer tracepoint is enabled. nilfs_grab_buffer() can restore an uptodate buffer without assigning bh->b_bdev, while mark_buffer_dirty() dereferences bh->b_bdev->bd_dev unconditionally. Reachability requires local access, NILFS2 metadata activity, and the enabled tracepoint; exploitation affects availability without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in Linux kernel NILFS2 allows local users to crash the system when the block_dirty_buffer tracepoint is enabled. nilfs_grab_buffer() can restore an uptodate buffer without assigning bh->b_bdev, while mark_buffer_dirty() dereferences bh->b_bdev->bd_dev unconditionally. Reachability requires local access, NILFS2 metadata activity, and the enabled tracepoint; exploitation affects availability without reported data disclosure or modification.
The record
- CVE
- CVE-2024-53130
- Published
- Dec 4, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 4, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.9
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <0a5014ad37c77ac6a2c525137c00a0e1724f6020
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <0ce59fb1c73fdd5b6028226aeb46259a0cdc0957
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <2026559a6c4ce34db117d2db8f710fe2a9420d5a
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <7af3309c7a2ef26831a67125b11c34a7e01c1b2a
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <86b19031dbc79abc378dfae357f6ea33ebeb0c95
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <b0e4765740040c44039282057ecacd7435d1d2ba
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <d904e4d845aafbcfd8a40c1df7d999f02f062be8
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <ffc440a76a0f476a7e6ea838ec0dc8e9979944d1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo