CVE-2024-53131: nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint

Published Dec 4, 2024
·
Updated

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

nilfs2: fix null-ptr-deref in blocktouchbuffer tracepoint

Patch series "nilfs2: fix null-ptr-deref bugs on block tracepoints".

This series fixes null pointer dereference bugs that occur when using nilfs2 and two block-related tracepoints.

This patch (of 2):

It has been reported that when using "block:blocktouchbuffer" tracepoint, touchbuffer() called from nilfsgetfolioblock() causes a NULL pointer dereference, or a general protection fault when KASAN is enabled.

This happens because since the tracepoint was added in touchbuffer(), 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, the blockdevice structure is set after the function returns to the caller.

Here, touchbuffer() is used to mark the folio/page that owns the buffer head as accessed, but the common search helper for folio/page used by the caller function was optimized to mark the folio/page as accessed when it was reimplemented a long time ago, eliminating the need to call touchbuffer() here in the first place.

So this solves the issue by eliminating the touchbuffer() call itself.

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-53131?

CVE-2024-53131 has a severity rating that indicates it can lead to null pointer dereference vulnerabilities in the Linux kernel.

2

How do I fix CVE-2024-53131?

To fix CVE-2024-53131, you should update your Linux kernel to a version that includes the patches, such as 6.1.123-1 or newer.

3

Which versions of the Linux kernel are affected by CVE-2024-53131?

CVE-2024-53131 affects versions from 3.9 to 6.1.119, 6.6.0 to 6.6.63, and 6.11.0 to 6.11.10.

4

What component of Linux is impacted by CVE-2024-53131?

CVE-2024-53131 impacts the nilfs2 file system within the Linux kernel.

5

Can CVE-2024-53131 cause system crashes?

Yes, CVE-2024-53131 can result in null pointer dereference which may lead to system crashes or instability.

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