Page 130 of 2704 results (0.008 seconds)

CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0

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: 0

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: 0

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 •

CVSS: -EPSS: 0%CPEs: 3EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: HID: nvidia-shield: Add missing null pointer checks to LED initialization 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. [jkosina@suse.com: tweak changelog a bit] En el kernel de Linux, se resolvió la siguiente vulnerabilidad: HID: nvidia-shield: agregar comprobaciones de puntero nulo faltantes a la inicialización del LED 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. [jkosina@suse.com: modificar un poco el registro de cambios] • https://git.kernel.org/stable/c/83527a13740f57b45f162e3af4c7db4b88521100 https://git.kernel.org/stable/c/e71cc4a1e584293deafff1a7dea614b0210d0443 https://git.kernel.org/stable/c/b6eda11c44dc89a681e1c105f0f4660e69b1e183 •

CVSS: 4.4EPSS: 0%CPEs: 5EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: avoid deadlock on delete association path When deleting an association the shutdown path is deadlocking because we try to flush the nvmet_wq nested. Avoid this by deadlock by deferring the put work into its own work item. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: nvmet-fc: evita el punto muerto al eliminar la ruta de asociación Al eliminar una asociación, la ruta de cierre se bloquea porque intentamos vaciar el nvmet_wq anidado. Evite este punto muerto al diferir el trabajo colocado en su propio elemento de trabajo. • https://git.kernel.org/stable/c/5e0bc09a52b6169ce90f7ac6e195791adb16cec4 https://git.kernel.org/stable/c/9e6987f8937a7bd7516aa52f25cb7e12c0c92ee8 https://git.kernel.org/stable/c/eaf0971fdabf2a93c1429dc6bedf3bbe85dffa30 https://git.kernel.org/stable/c/1d86f79287206deec36d63b89c741cf542b6cadd https://git.kernel.org/stable/c/710c69dbaccdac312e32931abcb8499c1525d397 https://access.redhat.com/security/cve/CVE-2024-26769 https://bugzilla.redhat.com/show_bug.cgi?id=2273180 • CWE-833: Deadlock •