cbcvebase.
CVE-2024-53130
published 2024-12-04

CVE-2024-53130: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint When using the…

PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
13.8th percentile
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.

Affected

28 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.119-1 (bookworm)linux 6.1.119-1 (bookworm)
debianlinux-6.1< linux 6.1.119-1 (bookworm)linux 6.1.119-1 (bookworm)
linuxlinux
linuxlinux>= 5305cb830834549b9203ad4d009ad5483c5e293f < 7af3309c7a2ef26831a67125b11c34a7e01c1b2a7af3309c7a2ef26831a67125b11c34a7e01c1b2a
linuxlinux>= 5305cb830834549b9203ad4d009ad5483c5e293f < 0ce59fb1c73fdd5b6028226aeb46259a0cdc09570ce59fb1c73fdd5b6028226aeb46259a0cdc0957
linuxlinux>= 5305cb830834549b9203ad4d009ad5483c5e293f < 0a5014ad37c77ac6a2c525137c00a0e1724f60200a5014ad37c77ac6a2c525137c00a0e1724f6020
linuxlinux>= 5305cb830834549b9203ad4d009ad5483c5e293f < d904e4d845aafbcfd8a40c1df7d999f02f062be8d904e4d845aafbcfd8a40c1df7d999f02f062be8
linuxlinux>= 5305cb830834549b9203ad4d009ad5483c5e293f < 86b19031dbc79abc378dfae357f6ea33ebeb0c9586b19031dbc79abc378dfae357f6ea33ebeb0c95
linuxlinux>= 5305cb830834549b9203ad4d009ad5483c5e293f < b0e4765740040c44039282057ecacd7435d1d2bab0e4765740040c44039282057ecacd7435d1d2ba
linuxlinux>= 5305cb830834549b9203ad4d009ad5483c5e293f < ffc440a76a0f476a7e6ea838ec0dc8e9979944d1ffc440a76a0f476a7e6ea838ec0dc8e9979944d1
linuxlinux>= 5305cb830834549b9203ad4d009ad5483c5e293f < 2026559a6c4ce34db117d2db8f710fe2a9420d5a2026559a6c4ce34db117d2db8f710fe2a9420d5a
linuxlinux_kernel>= 0 < 5.10.234-15.10.234-1
linuxlinux_kernel>= 0 < 6.1.119-16.1.119-1
linuxlinux_kernel>= 0 < 6.11.10-16.11.10-1
linuxlinux_kernel>= 0 < 6.11.10-16.11.10-1
linuxlinux_kernel>= 0 < 5.4.0-211.2315.4.0-211.231
linuxlinux_kernel>= 0 < 5.15.0-135.1465.15.0-135.146
linuxlinux_kernel>= 0 < 6.8.0-58.606.8.0-58.60
linuxlinux_kernel>= 0 < 6.11.0-18.186.11.0-18.18
linuxlinux_kernel>= 0 < 4.4.0-272.3064.4.0-272.306
linuxlinux_kernel>= 0 < 4.15.0-241.2534.15.0-241.253
linuxlinux_kernel>= 3.9 < 6.1.1196.1.119
linuxlinux_kernel>= 6.11.0 < 6.11.106.11.10
linuxlinux_kernel>= 6.6.0 < 6.6.636.6.63
msrcazl3_kernel_6.6.57.1-7_on_azure_linux_3.0

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_debian5.5MEDIUM
vendor_msrc5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.