CVE-2024-53130

Description

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.

Gravité et risque d'exploitation

CVE-2024-53130 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.24 %, ce qui la place devant 13.6 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions 6.12, <=6.1.*, <=6.11.*, 6.1.119, 0, <3.9, <ffc440a76a0f476a7e6ea838ec0dc8e9979944d1, 3.9, 5.10.231, 5.15.174, 6.11.10, <7af3309c7a2ef26831a67125b11c34a7e01c1b2a, <=5.10.*, <=6.6.*, 6.6.63, <2026559a6c4ce34db117d2db8f710fe2a9420d5a, <0ce59fb1c73fdd5b6028226aeb46259a0cdc0957, <=5.4.*, <=4.19.*, <b0e4765740040c44039282057ecacd7435d1d2ba, <86b19031dbc79abc378dfae357f6ea33ebeb0c95, 5305cb830834549b9203ad4d009ad5483c5e293f, <d904e4d845aafbcfd8a40c1df7d999f02f062be8, <=*, <=5.15.*, 5.4.287, <0a5014ad37c77ac6a2c525137c00a0e1724f6020, 4.19.325) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/7af3309c7a2ef26831a67125b11c34a7e01c1b2a
• https://git.kernel.org/stable/c/0ce59fb1c73fdd5b6028226aeb46259a0cdc0957
• https://git.kernel.org/stable/c/0a5014ad37c77ac6a2c525137c00a0e1724f6020
• https://git.kernel.org/stable/c/d904e4d845aafbcfd8a40c1df7d999f02f062be8
• https://git.kernel.org/stable/c/86b19031dbc79abc378dfae357f6ea33ebeb0c95
• https://git.kernel.org/stable/c/b0e4765740040c44039282057ecacd7435d1d2ba
• https://git.kernel.org/stable/c/ffc440a76a0f476a7e6ea838ec0dc8e9979944d1
• https://git.kernel.org/stable/c/2026559a6c4ce34db117d2db8f710fe2a9420d5a