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

Published Dec 4, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

nilfs2: fix null-ptr-deref in blockdirtybuffer tracepoint

When using the "block:blockdirtybuffer" tracepoint, markbufferdirty() may cause a NULL pointer dereference, or a general protection fault when KASAN is enabled.

This happens because, since the tracepoint was added in markbufferdirty(), it references the devt member bh->bbdev->bddev regardless of whether the buffer head has a pointer to a blockdevice structure.

In the current implementation, nilfsgrabbuffer(), 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 trytofreebuffers(), and new buffer heads are then attached by createemptybuffers(), the uptodate flag may be restored to each buffer without the block device being set to bh->bbdev, and markbufferdirty() may be called later in that state, resulting in the bug mentioned above.

Fix this issue by making nilfsgrabbuffer() always set the block device of the super block structure to the buffer head, regardless of the state of the buffer's uptodate flag.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

5 affected componentsFixes available
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
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1

Event History

Dec 4, 2024
CVE Published
via MITRE·02:20 PM
Data Sourced
via MITRE·02:20 PM
Description
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 20, 2025
Data Sourced
via Launchpad·12:52 AM
Description
Apr 29, 2025
Data Sourced
via Ubuntu·01:09 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203