CVSS: 7.0EPSS: 0%CPEs: 5EXPL: 0CVE-2024-27035 – f2fs: compress: fix to guarantee persisting compressed blocks by CP
https://notcve.org/view.php?id=CVE-2024-27035
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: fix to guarantee persisting compressed blocks by CP If data block in compressed cluster is not persisted with metadata during checkpoint, after SPOR, the data may be corrupted, let's guarantee to write compressed page by checkpoint. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: f2fs: compress: corrección para garantizar la persistencia de los bloques comprimidos por CP. Si el bloque de datos en el clúste... • https://git.kernel.org/stable/c/4c8ff7095bef64fc47e996a938f7d57f9e077da3 •
CVSS: 7.0EPSS: 0%CPEs: 6EXPL: 0CVE-2024-27034 – f2fs: compress: fix to cover normal cluster write with cp_rwsem
https://notcve.org/view.php?id=CVE-2024-27034
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: fix to cover normal cluster write with cp_rwsem When we overwrite compressed cluster w/ normal cluster, we should not unlock cp_rwsem during f2fs_write_raw_pages(), otherwise data will be corrupted if partial blocks were persisted before CP & SPOR, due to cluster metadata wasn't updated atomically. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: f2fs: compress: corrección para cubrir la escritura normal del c... • https://git.kernel.org/stable/c/4c8ff7095bef64fc47e996a938f7d57f9e077da3 •
CVSS: 7.0EPSS: 0%CPEs: 4EXPL: 0CVE-2024-27033 – f2fs: fix to remove unnecessary f2fs_bug_on() to avoid panic
https://notcve.org/view.php?id=CVE-2024-27033
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to remove unnecessary f2fs_bug_on() to avoid panic verify_blkaddr() will trigger panic once we inject fault into f2fs_is_valid_blkaddr(), fix to remove this unnecessary f2fs_bug_on(). En el kernel de Linux, se resolvió la siguiente vulnerabilidad: f2fs: solución para eliminar f2fs_bug_on() innecesario para evitar el pánico. verificar_blkaddr() provocará pánico una vez que inyectemos el error en f2fs_is_valid_blkaddr(), solución pa... • https://git.kernel.org/stable/c/18792e64c86dd7e34ba28e4f61faba472b7bf5fc •
CVSS: 7.0EPSS: 0%CPEs: 9EXPL: 0CVE-2024-27032 – f2fs: fix to avoid potential panic during recovery
https://notcve.org/view.php?id=CVE-2024-27032
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid potential panic during recovery During recovery, if FAULT_BLOCK is on, it is possible that f2fs_reserve_new_block() will return -ENOSPC during recovery, then it may trigger panic. Also, if fault injection rate is 1 and only FAULT_BLOCK fault type is on, it may encounter deadloop in loop of block reservation. Let's change as below to fix these issues: - remove bug_on() to avoid panic. - limit the loop count of block reserv... • https://git.kernel.org/stable/c/b1020a546779139eec5d930e15ce534c1101b89c •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-27031 – NFS: Fix nfs_netfs_issue_read() xarray locking for writeback interrupt
https://notcve.org/view.php?id=CVE-2024-27031
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: NFS: Fix nfs_netfs_issue_read() xarray locking for writeback interrupt The loop inside nfs_netfs_issue_read() currently does not disable interrupts while iterating through pages in the xarray to submit for NFS read. This is not safe though since after taking xa_lock, another page in the mapping could be processed for writeback inside an interrupt, and deadlock can occur. The fix is simple and clean if we use xa_for_each_range(), which handl... • https://git.kernel.org/stable/c/000dbe0bec058cbf2ca9e156e4a5584f5158b0f9 •
CVSS: 5.8EPSS: 0%CPEs: 8EXPL: 0CVE-2024-27030 – octeontx2-af: Use separate handlers for interrupts
https://notcve.org/view.php?id=CVE-2024-27030
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: Use separate handlers for interrupts For PF to AF interrupt vector and VF to AF vector same interrupt handler is registered which is causing race condition. When two interrupts are raised to two CPUs at same time then two cores serve same event corrupting the data. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: octeontx2-af: utilice controladores separados para las interrupciones. Para el vector de interrupció... • https://git.kernel.org/stable/c/7304ac4567bcb72fd57cc79582bf53ca7840136f •
CVSS: 6.5EPSS: 0%CPEs: 9EXPL: 0CVE-2024-27028 – spi: spi-mt65xx: Fix NULL pointer access in interrupt handler
https://notcve.org/view.php?id=CVE-2024-27028
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: spi: spi-mt65xx: Fix NULL pointer access in interrupt handler The TX buffer in spi_transfer can be a NULL pointer, so the interrupt handler may end up writing to the invalid memory and cause crashes. Add a check to trans->tx_buf before using it. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: spi: spi-mt65xx: corrige el acceso al puntero NULL en el controlador de interrupciones. El búfer TX en spi_transfer puede ser un pu... • https://git.kernel.org/stable/c/1ce24864bff40e11500a699789412115fdf244bf • CWE-476: NULL Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2023-52650 – drm/tegra: dsi: Add missing check for of_find_device_by_node
https://notcve.org/view.php?id=CVE-2023-52650
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: drm/tegra: dsi: Add missing check for of_find_device_by_node Add check for the return value of of_find_device_by_node() and return the error if it fails in order to avoid NULL pointer dereference. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: drm/tegra: dsi: Agregar verificación faltante para of_find_device_by_node Agregue verificación para el valor de retorno de of_find_device_by_node() y devuelva el error si falla para e... • https://git.kernel.org/stable/c/e94236cde4d519cdecd45e2435defba33abdc99f •
CVSS: 7.0EPSS: 0%CPEs: 4EXPL: 0CVE-2023-52649 – drm/vkms: Avoid reading beyond LUT array
https://notcve.org/view.php?id=CVE-2023-52649
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: drm/vkms: Avoid reading beyond LUT array When the floor LUT index (drm_fixp2int(lut_index) is the last index of the array the ceil LUT index will point to an entry beyond the array. Make sure we guard against it and use the value of the floor LUT index. v3: - Drop bits from commit description that didn't contribute anything of value En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/vkms: Evite leer más allá de la matriz... • https://git.kernel.org/stable/c/db1f254f2cfaf0510ae34fa2311a8d749e95179a •
CVSS: 7.0EPSS: 0%CPEs: 4EXPL: 0CVE-2024-27026 – vmxnet3: Fix missing reserved tailroom
https://notcve.org/view.php?id=CVE-2024-27026
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: vmxnet3: Fix missing reserved tailroom Use rbi->len instead of rcd->len for non-dataring packet. Found issue: XDP_WARN: xdp_update_frame_from_buff(line:278): Driver BUG: missing reserved tailroom WARNING: CPU: 0 PID: 0 at net/core/xdp.c:586 xdp_warn+0xf/0x20 CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W O 6.5.1 #1 RIP: 0010:xdp_warn+0xf/0x20 ... ? xdp_warn+0xf/0x20 xdp_do_redirect+0x15f/0x1c0 vmxnet3_run_xdp+0x17a/0x400 [vmxnet3] vmxnet3_proce... • https://git.kernel.org/stable/c/54f00cce11786742bd11e5e68c3bf85e6dc048c9 •