CWE
476
Advisory Published
Updated

CVE-2024-53130: nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint

First published: Wed Dec 04 2024(Updated: )

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.

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=3.9<6.1.119
Linux Kernel>=6.6.0<6.6.63
Linux Kernel>=6.11.0<6.11.10
debian/linux<=5.10.223-1<=5.10.226-1
6.1.123-1
6.1.128-1
6.12.12-1
6.12.15-1
debian/linux-6.1
6.1.119-1~deb11u1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-53130?

    CVE-2024-53130 has a severity level classified as critical due to the potential for NULL pointer dereference leading to denial of service.

  • How do I fix CVE-2024-53130?

    To fix CVE-2024-53130, update the Linux kernel to versions greater than 6.1.119, between 6.6.0 and 6.6.63, or between 6.11.0 and 6.11.10.

  • Which Linux kernel versions are affected by CVE-2024-53130?

    CVE-2024-53130 affects Linux kernel versions from 3.9 up to 6.1.119, from 6.6.0 to 6.6.63, and from 6.11.0 to 6.11.10.

  • What components are involved in CVE-2024-53130?

    CVE-2024-53130 involves the nilfs2 file system and the block_dirty_buffer tracepoint in the Linux kernel.

  • Is CVE-2024-53130 being actively exploited?

    As of now, there is no public indication that CVE-2024-53130 is being actively exploited.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203