CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-27041 – drm/amd/display: fix NULL checks for adev->dm.dc in amdgpu_dm_fini()
https://notcve.org/view.php?id=CVE-2024-27041
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix NULL checks for adev->dm.dc in amdgpu_dm_fini() Since 'adev->dm.dc' in amdgpu_dm_fini() might turn out to be NULL before the call to dc_enable_dmub_notifications(), check beforehand to ensure there will not be a possible NULL-ptr-deref there. Also, since commit 1e88eb1b2c25 ("drm/amd/display: Drop CONFIG_DRM_AMD_DC_HDCP") there are two separate checks for NULL in 'adev->dm.dc' before dc_deinit_callbacks() and dc_dmub_sr... • https://git.kernel.org/stable/c/81927e2808be5adace93c2012d45d6938d3a7aa0 • CWE-476: NULL Pointer Dereference •
CVSS: 6.9EPSS: 0%CPEs: 4EXPL: 0CVE-2024-27040 – drm/amd/display: Add 'replay' NULL check in 'edp_set_replay_allow_active()'
https://notcve.org/view.php?id=CVE-2024-27040
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add 'replay' NULL check in 'edp_set_replay_allow_active()' In the first if statement, we're checking if 'replay' is NULL. But in the second if statement, we're not checking if 'replay' is NULL again before calling replay->funcs->replay_set_power_opt(). if (replay == NULL && force_static) return false; ... if (link->replay_settings.replay_feature_enabled && replay->funcs->replay_set_power_opt) { replay->funcs->replay_set_pow... • https://git.kernel.org/stable/c/c7ddc0a800bc9f681a18c3bdd9f06b61adfabc11 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2024-27039 – clk: hisilicon: hi3559a: Fix an erroneous devm_kfree()
https://notcve.org/view.php?id=CVE-2024-27039
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: clk: hisilicon: hi3559a: Fix an erroneous devm_kfree() 'p_clk' is an array allocated just before the for loop for all clk that need to be registered. It is incremented at each loop iteration. If a clk_register() call fails, 'p_clk' may point to something different from what should be freed. The best we can do, is to avoid this wrong release of memory. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: clk: hisilicon: hi3559a: c... • https://git.kernel.org/stable/c/6c81966107dc0caa5d2ebedbcebb5f10d865064d •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2024-27038 – clk: Fix clk_core_get NULL dereference
https://notcve.org/view.php?id=CVE-2024-27038
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: clk: Fix clk_core_get NULL dereference It is possible for clk_core_get to dereference a NULL in the following sequence: clk_core_get() of_clk_get_hw_from_clkspec() __of_clk_get_hw_from_provider() __clk_get_hw() __clk_get_hw() can return NULL which is dereferenced by clk_core_get() at hw->core. Prior to commit dde4eff47c82 ("clk: Look for parents with clkdev based clk_lookups") the check IS_ERR_OR_NULL() was performed which would have caught... • https://git.kernel.org/stable/c/dde4eff47c82c52a72af333d9e55370eee6d95d6 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2024-27037 – clk: zynq: Prevent null pointer dereference caused by kmalloc failure
https://notcve.org/view.php?id=CVE-2024-27037
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: clk: zynq: Prevent null pointer dereference caused by kmalloc failure The kmalloc() in zynq_clk_setup() will return null if the physical memory has run out. As a result, if we use snprintf() to write data to the null address, the null pointer dereference bug will happen. This patch uses a stack variable to replace the kmalloc(). En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: clk: zynq: evita la desreferencia del puntero ... • https://git.kernel.org/stable/c/0ee52b157b8ed88550ddd6291e54bb4bfabde364 • CWE-476: NULL Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-27036 – cifs: Fix writeback data corruption
https://notcve.org/view.php?id=CVE-2024-27036
01 May 2024 — In the Linux kernel, the following vulnerability has been resolved: cifs: Fix writeback data corruption cifs writeback doesn't correctly handle the case where cifs_extend_writeback() hits a point where it is considering an additional folio, but this would overrun the wsize - at which point it drops out of the xarray scanning loop and calls xas_pause(). The problem is that xas_pause() advances the loop counter - thereby skipping that page. What needs to happen is for xas_reset() to be called any time we deci... • https://git.kernel.org/stable/c/d08089f649a0cfb2099c8551ac47eef0cc23fdf2 •
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 •