VDB

CVE-2024-53131

CVE-2024-53131 PUBLISHED

nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint

Reported by linux · Published December 4, 2024

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix null-ptr-deref in block_touch_buffer 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:block_touch_buffer" tracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a NULL pointer dereference, or a general protection fault when KASAN is enabled. This happens because since the tracepoint was added in touch_buffer(), 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, the block_device structure is set after the function returns to the caller. Here, touch_buffer() 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 touch_buffer() here in the first place. So this solves the issue by eliminating the touch_buffer() call itself.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel-modules-extra-commonAmazon Linux6.1.119-129.201.amzn2023
kernel-libbpf-develAmazon Linux6.1.119-129.201.amzn2023
kernel-libbpf-staticAmazon Linux6.1.119-129.201.amzn2023
perfAmazon Linux6.1.119-129.201.amzn2023
kernel-modules-extraAmazon Linux6.1.119-129.201.amzn2023

Affected products

VendorProductVersions
LinuxLinux5305cb830834549b9203ad4d009ad5483c5e293f, 5305cb830834549b9203ad4d009ad5483c5e293f, 5305cb830834549b9203ad4d009ad5483c5e293f
LinuxLinux3.9, 0, 4.19.325
amazon:2023kernel-modules-extra-common0
amazon:2023kernel-libbpf-devel0
amazon:2023kernel-libbpf-static0
amazon:2023perf0
amazon:2023kernel-modules-extra0
linuxlinux_kernel3.9, 3.9, 3.9
amazon:2023bpftool0
amazon:2023python3-perf0
amazon:2023kernel0
amazon:2023kernel-headers0
amazon:2023kernel-tools-devel0
LinuxLinux6.1.119, 5305cb830834549b9203ad4d009ad5483c5e293f, 6.6.63
amazon:2023kernel-libbpf0
amazon:2023kernel-tools0
amazon:2023kernel-devel0
amazon:2023kernel-livepatch-6.1.119-129.2010

Timeline

  • Dec 4, 2024 Coalition ESS Score (12 in total, the first dated here)
  • Dec 4, 2024 CVE Published
  • Dec 5, 2024 EPSS Score (30 in total, the first dated here)
  • Jan 6, 2025 CVE Updated
  • Dec 16, 2025 PoC Published
  • Dec 31, 2025 Security Advisory (180 in total, the first dated here)
  • Apr 29, 2026 Distribution Patch (160 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2024-53131
vulnetix vdb fixes CVE-2024-53131

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-53131/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›