Kernel crash via premature block-device dereference
Published Dec 4, 2024 · Updated May 11, 2026
NULL pointer dereference in Linux nilfs2 allows local users to crash the kernel by enabling the block_touch_buffer tracepoint. touch_buffer(), called from __nilfs_get_folio_block(), passes a buffer head to the tracepoint before bh->b_bdev is assigned, and the tracepoint dereferences bh->b_bdev->bd_dev. The path requires local low-privileged access, an active nilfs2 filesystem, and the enabled tracepoint; the reported result is a crash or KASAN general protection fault.
Summary
What happened
NULL pointer dereference in Linux nilfs2 allows local users to crash the kernel by enabling the block_touch_buffer tracepoint. touch_buffer(), called from __nilfs_get_folio_block(), passes a buffer head to the tracepoint before bh->b_bdev is assigned, and the tracepoint dereferences bh->b_bdev->bd_dev. The path requires local low-privileged access, an active nilfs2 filesystem, and the enabled tracepoint; the reported result is a crash or KASAN general protection fault.
The record
- CVE
- CVE-2024-53131
- 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 <085556bf8c70e2629e02e79268dac3016a08b8bf
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <19c71cdd77973f99a9adc3190130bc3aa7ae5423
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <3b2a4fd9bbee77afdd3ed5a05a0c02b6cde8d3b9
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <59b49ca67cca7b007a5afd3de0283c8008157665
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <6438f3f42cda825f6f59b4e45ac3a1da28a6f2c9
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <77e47f89d32c2d72eb33d0becbce7abe14d061f4
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <b017697a517f8779ada4e8ce1c2c75dbf60a2636
- Affected versionversion=5305cb830834549b9203ad4d009ad5483c5e293f <cd45e963e44b0f10d90b9e6c0e8b4f47f3c92471
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