CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2024-26775 – aoe: avoid potential deadlock at set_capacity
https://notcve.org/view.php?id=CVE-2024-26775
In the Linux kernel, the following vulnerability has been resolved: aoe: avoid potential deadlock at set_capacity Move set_capacity() outside of the section procected by (&d->lock). To avoid possible interrupt unsafe locking scenario: CPU0 CPU1 ---- ---- [1] lock(&bdev->bd_size_lock); local_irq_disable(); [2] lock(&d->lock); [3] lock(&bdev->bd_size_lock); <Interrupt> [4] lock(&d->lock); *** DEADLOCK *** Where [1](&bdev->bd_size_lock) hold by zram_add()->set_capacity(). [2]lock(&d->lock) hold by aoeblk_gdalloc(). And aoeblk_gdalloc() is trying to acquire [3](&bdev->bd_size_lock) at set_capacity() call. In this situation an attempt to acquire [4]lock(&d->lock) from aoecmd_cfg_rsp() will lead to deadlock. So the simplest solution is breaking lock dependency [2](&d->lock) -> [3](&bdev->bd_size_lock) by moving set_capacity() outside. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: aoe: evita un posible punto muerto en set_capacity Mueve set_capacity() fuera de la sección procesada por (&d->lock). Para evitar una posible interrupción en un escenario de bloqueo inseguro: CPU0 CPU1 ---- ---- [1] lock(&bdev->bd_size_lock); local_irq_disable(); [2] bloquear(&d->bloquear); [3] bloquear(&bdev->bd_size_lock); [4] bloqueo(&d->bloqueo); *** DEADLOCK *** Donde [1](&bdev->bd_size_lock) mantenido por zram_add()->set_capacity(). [2]bloqueo(&d->bloqueo) retenido por aoeblk_gdalloc(). Y aoeblk_gdalloc() está intentando adquirir [3](&bdev->bd_size_lock) en la llamada set_capacity(). • https://git.kernel.org/stable/c/2d623c94fbba3554f4446ba6f3c764994e8b0d26 https://git.kernel.org/stable/c/673629018ba04906899dcb631beec34d871f709c https://git.kernel.org/stable/c/19a77b27163820f793b4d022979ffdca8f659b77 https://git.kernel.org/stable/c/e169bd4fb2b36c4b2bee63c35c740c85daeb2e86 •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-26774 – ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt
https://notcve.org/view.php?id=CVE-2024-26774
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt Determine if bb_fragments is 0 instead of determining bb_free to eliminate the risk of dividing by zero when the block bitmap is corrupted. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ext4: evitar dividir por 0 en mb_update_avg_fragment_size() cuando el mapa de bits del bloque está dañado. Determine si bb_fragments es 0 en lugar de determinar bb_free para eliminar el riesgo de dividir por cero cuando el mapa de bits del bloque está dañado. • https://git.kernel.org/stable/c/687061cfaa2ac3095170e136dd9c29a4974f41d4 https://git.kernel.org/stable/c/8b40eb2e716b503f7a4e1090815a17b1341b2150 https://git.kernel.org/stable/c/f32d2a745b02123258026e105a008f474f896d6a https://git.kernel.org/stable/c/8cf9cc602cfb40085967c0d140e32691c8b71cf3 https://git.kernel.org/stable/c/993bf0f4c393b3667830918f9247438a8f6fdb5b •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2024-26773 – ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()
https://notcve.org/view.php?id=CVE-2024-26773
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found() Determine if the group block bitmap is corrupted before using ac_b_ex in ext4_mb_try_best_found() to avoid allocating blocks from a group with a corrupted block bitmap in the following concurrency and making the situation worse. ext4_mb_regular_allocator ext4_lock_group(sb, group) ext4_mb_good_group // check if the group bbitmap is corrupted ext4_mb_complex_scan_group // Scan group gets ac_b_ex but doesn't use it ext4_unlock_group(sb, group) ext4_mark_group_bitmap_corrupted(group) // The block bitmap was corrupted during // the group unlock gap. ext4_mb_try_best_found ext4_lock_group(ac->ac_sb, group) ext4_mb_use_best_found mb_mark_used // Allocating blocks in block bitmap corrupted group En el kernel de Linux, se resolvió la siguiente vulnerabilidad: ext4: evite asignar bloques de un grupo dañado en ext4_mb_try_best_found() Determine si el mapa de bits del bloque del grupo está dañado antes de usar ac_b_ex en ext4_mb_try_best_found() para evitar asignar bloques de un grupo con un bloque dañado mapa de bits en la siguiente concurrencia y empeorando la situación. ext4_mb_regular_allocator ext4_lock_group(sb, group) ext4_mb_good_group // verifica si el bbitmap del grupo está dañado ext4_mb_complex_scan_group // El grupo de escaneo obtiene ac_b_ex pero no lo usa ext4_unlock_group(sb, group) ext4_mark_group_bitmap_corrupted(group) // El mapa de bits del bloque se corrompió durante // el grupo desbloquea la brecha. ext4_mb_try_best_found ext4_lock_group(ac->ac_sb, group) ext4_mb_use_best_found mb_mark_used // Asignación de bloques en un grupo dañado de mapa de bits de bloques A vulnerability was found in the ext4_mb_try_best_found() function in the Linux kernel. This issue could lead to memory corruption or crashes due to the allocation of blocks from a group with a corrupted block bitmap. • https://git.kernel.org/stable/c/21f8cfe79f776287459343e9cfa6055af61328ea https://git.kernel.org/stable/c/260fc96283c0f594de18a1b045faf6d8fb42874d https://git.kernel.org/stable/c/927794a02169778c9c2e7b25c768ab3ea8c1dc03 https://git.kernel.org/stable/c/4c21fa60a6f4606f6214a38f50612b17b2f738f5 https://git.kernel.org/stable/c/f97e75fa4e12b0aa0224e83fcbda8853ac2adf36 https://git.kernel.org/stable/c/0184747b552d6b5a14db3b7fcc3b792ce64dedd1 https://git.kernel.org/stable/c/a2576ae9a35c078e488f2c573e9e6821d651fbbe https://git.kernel.org/stable/c/4530b3660d396a646aad91a787b6ab37c • CWE-229: Improper Handling of Values •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2024-26772 – ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
https://notcve.org/view.php?id=CVE-2024-26772
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal() Places the logic for checking if the group's block bitmap is corrupt under the protection of the group lock to avoid allocating blocks from the group with a corrupted block bitmap. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ext4: evita asignar bloques del grupo corrupto en ext4_mb_find_by_goal() Coloca la lógica para verificar si el mapa de bits del bloque del grupo está corrupto bajo la protección del bloqueo del grupo para evitar la asignación de bloques del grupo con un mapa de bits de bloque dañado. A vulnerability was found in the ext4_mb_find_by_goal() function in the Linux kernel. This issue could lead to memory corruption or crashes due to the allocation of blocks from a group with a corrupted block bitmap. • https://git.kernel.org/stable/c/5a6dcc4ad0f7f7fa8e8d127b5526e7c5f2d38a43 https://git.kernel.org/stable/c/6b92b1bc16d691c95b152c6dbf027ad64315668d https://git.kernel.org/stable/c/ffeb72a80a82aba59a6774b0611f792e0ed3b0b7 https://git.kernel.org/stable/c/8de8305a25bfda607fc13475ebe84b978c96d7ff https://git.kernel.org/stable/c/d639102f4cbd4cb65d1225dba3b9265596aab586 https://git.kernel.org/stable/c/d3bbe77a76bc52e9d4d0a120f1509be36e25c916 https://git.kernel.org/stable/c/21dbe20589c7f48e9c5d336ce6402bcebfa6d76a https://git.kernel.org/stable/c/832698373a25950942c04a512daa652c1 • CWE-229: Improper Handling of Values •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2024-26771 – dmaengine: ti: edma: Add some null pointer checks to the edma_probe
https://notcve.org/view.php?id=CVE-2024-26771
In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: edma: Add some null pointer checks to the edma_probe devm_kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. Ensure the allocation was successful by checking the pointer validity. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: dmaengine: ti: edma: agregue algunas comprobaciones de puntero nulo a edma_probe devm_kasprintf() devuelve un puntero a la memoria asignada dinámicamente que puede ser NULL en caso de falla. Asegúrese de que la asignación se haya realizado correctamente comprobando la validez del puntero. • https://git.kernel.org/stable/c/c432094aa7c9970f2fa10d2305d550d3810657ce https://git.kernel.org/stable/c/4fe4e5adc7d29d214c59b59f61db73dec505ca3d https://git.kernel.org/stable/c/9d508c897153ae8dd79303f7f035f078139f6b49 https://git.kernel.org/stable/c/7b24760f3a3c7ae1a176d343136b6c25174b7b27 https://git.kernel.org/stable/c/f2a5e30d1e9a629de6179fa23923a318d5feb29e https://git.kernel.org/stable/c/6e2276203ac9ff10fc76917ec9813c660f627369 https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html •