CVE-2024-53130
Last modified
CVE-2024-53130 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 3.9, < 6.1.119 |
| Linux | Linux Kernel | >= 6.6.0, < 6.6.63 |
| Linux | Linux Kernel | >= 6.11.0, < 6.11.10 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-53130?
How severe is CVE-2024-53130?
How do I fix CVE-2024-53130?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-53125In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-53126In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-53127In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-53128In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-53129In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5313CWE-668: Exposure of the Resource Wrong Sphere vulnerability…6.5
- CVE-2024-53131In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-53132In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-53133In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-53134In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-53135In the Linux kernel, the following vulnerability has been re…6.5
- CVE-2024-53136In the Linux kernel, the following vulnerability has been re…4.7
Are you affected by CVE-2024-53130?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
