CVE-2024-38598
Vulnérabilité non évaluée dans Linux (Linux)
Description
In the Linux kernel, the following vulnerability has been resolved: md: fix resync softlockup when bitmap size is less than array size Is is reported that for dm-raid10, lvextend + lvchange --syncaction will trigger following softlockup: kernel:watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [mdX_resync:6976] CPU: 7 PID: 3588 Comm: mdX_resync Kdump: loaded Not tainted 6.9.0-rc4-next-20240419 #1 RIP: 0010:_raw_spin_unlock_irq+0x13/0x30 Call Trace: <TASK> md_bitmap_start_sync+0x6b/0xf0 raid10_sync_request+0x25c/0x1b40 [raid10] md_do_sync+0x64b/0x1020 md_thread+0xa7/0x170 kthread+0xcf/0x100 ret_from_fork+0x30/0x50 ret_from_fork_asm+0x1a/0x30 And the detailed process is as follows: md_do_sync j = mddev->resync_min while (j < max_sectors) sectors = raid10_sync_request(mddev, j, &skipped) if (!md_bitmap_start_sync(..., &sync_blocks)) // md_bitmap_start_sync set sync_blocks to 0 return sync_blocks + sectors_skippe; // sectors = 0; j += sectors; // j never change Root cause is that commit 301867b1c168 ("md/raid10: check slab-out-of-bounds in md_bitmap_get_counter") return early from md_bitmap_get_counter(), without setting returned blocks. Fix this problem by always set returned blocks from md_bitmap_get_counter"(), as it used to be. Noted that this patch just fix the softlockup problem in kernel, the case that bitmap size doesn't match array size still need to be fixed.
Gravité et risque d'exploitation
CVE-2024-38598 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.20 %, ce qui la place devant 8.8 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions bea301c046110bf421a3ce153fb868cb8d618e90, 6.3.13, <=6.1.*, 6.10, <f0e729af2eb6bee9eb58c4df1087f14ebaefe26b, 5.4.251, <6.5, 0, <d4b9c764d48fa41caa24cfb4275f3aa9fb4bd798, <c9566b812c8f66160466cc1e29df6d3646add0b1, 5.15.121, 374fb914304d9b500721007f3837ea8f1f9a2418, 39fa14e824acfd470db4f42c354297456bd82b53, <69296914bfd508c85935bf5f711cad9b0fe78492, 6.5, <=5.10.*, <=6.6.*, 6.8.12, <=6.9.*, b0b971fe7d61411ede63c3291764dbde1577ef2c, <6.4, 5.10.219, 4.19.316, <3f5b73ef8fd6268cbc968b308d8eafe56fda97f3, <=5.4.*, 6.6.33, <=4.19.*, <5817f43ae1a118855676f57ef7ab50e37eac7482, 5.4.278, 5.15.161, 301867b1c16805aebbc306aafa6ecdc68b73c7e5, <5.15.161, <8bbc71315e0ae4bb7e37f8d43b915e1cb01a481b, <=6.8.*, 152bb26796ff054af50b2ee1b3ca56e364e4f61b, 6.4.4, <6.1.93, 6.1.93, <43771597feba89a839c5f893716df88ae5c237ce, <71e8e4f288e74a896b6d9cd194f3bab12bd7a10f, <=*, <5.10.219, <=5.15.*, 4.19.291, a134dd582c0d5b6068efa308bd485cf1d00b3f65, <5.4.278, 5.10.188, <4.19.316, 6.9.3, be1a3ec63a840cc9e59a033acf154f56255699a1, 6.1.39) 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/d4b9c764d48fa41caa24cfb4275f3aa9fb4bd798
- https://git.kernel.org/stable/c/43771597feba89a839c5f893716df88ae5c237ce
- https://git.kernel.org/stable/c/3f5b73ef8fd6268cbc968b308d8eafe56fda97f3
- https://git.kernel.org/stable/c/69296914bfd508c85935bf5f711cad9b0fe78492
- https://git.kernel.org/stable/c/71e8e4f288e74a896b6d9cd194f3bab12bd7a10f
- https://git.kernel.org/stable/c/c9566b812c8f66160466cc1e29df6d3646add0b1
- https://git.kernel.org/stable/c/5817f43ae1a118855676f57ef7ab50e37eac7482
- https://git.kernel.org/stable/c/8bbc71315e0ae4bb7e37f8d43b915e1cb01a481b
- https://git.kernel.org/stable/c/f0e729af2eb6bee9eb58c4df1087f14ebaefe26b