nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5305cb830834549b9203ad4d009ad5483c5e293f · < 59b49ca67cca7b007a5afd3de0283c8008157665| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel can dereference a NULL pointer when nilfs2 calls touch_buffer() while the block:block_touch_buffer tracepoint is in use. This can cause a fault because the tracepoint accesses a block-device pointer before it is set. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with nilfs2 should check their kernel versions; affected versions are not specified.