CVSS: -EPSS: 0%CPEs: 9EXPL: 0CVE-2023-52875 – clk: mediatek: clk-mt2701: Add check for mtk_alloc_clk_data
https://notcve.org/view.php?id=CVE-2023-52875
In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt2701: Add check for mtk_alloc_clk_data Add the check for the return value of mtk_alloc_clk_data() in order to avoid NULL pointer dereference. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: clk: mediatek: clk-mt2701: Agregar verificación para mtk_alloc_clk_data. Agregue la verificación para el valor de retorno de mtk_alloc_clk_data() para evitar la desreferencia al puntero NULL. • https://git.kernel.org/stable/c/e9862118272aa528e35e54ef9f1e35c217870fd7 https://git.kernel.org/stable/c/6fccee2af400edaed9cf349d506c5971d4762739 https://git.kernel.org/stable/c/1953e62366da5460dc712e045f94fb0d8918999d https://git.kernel.org/stable/c/d1461f0c9ca0827c03730fe9652ebbf6316a2a95 https://git.kernel.org/stable/c/001e5def774fa1a8f2b29567c0b0cd3e3a859a96 https://git.kernel.org/stable/c/d1175cf4bd2b4c5f7c43f677ea1ce9ad2c18d055 https://git.kernel.org/stable/c/2a18dd653284550900b02107c3c7b3ac5e0eb802 https://git.kernel.org/stable/c/e61934720af4a58ffd43a63ffdd6f3a0b •
CVSS: -EPSS: 0%CPEs: 7EXPL: 0CVE-2023-52873 – clk: mediatek: clk-mt6779: Add check for mtk_alloc_clk_data
https://notcve.org/view.php?id=CVE-2023-52873
In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt6779: Add check for mtk_alloc_clk_data Add the check for the return value of mtk_alloc_clk_data() in order to avoid NULL pointer dereference. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: clk: mediatek: clk-mt6779: Agregar verificación para mtk_alloc_clk_data. Agregue la verificación para el valor de retorno de mtk_alloc_clk_data() para evitar la desreferencia al puntero NULL. • https://git.kernel.org/stable/c/710774e048614c761a39a98e8d0fa75f688c83b6 https://git.kernel.org/stable/c/fbe466f06d4ea18745da0d57540539b7b36936ae https://git.kernel.org/stable/c/3994387ba3564976731179c4d4a6d7850ddda71a https://git.kernel.org/stable/c/ca6d565a2319d69d9766e6ecbb5af827fc4afb2b https://git.kernel.org/stable/c/df1c4a9efa3f5b6fb5e0ae63890230dbe2190b7e https://git.kernel.org/stable/c/a90239551abc181687f8c0ba60b276f7d75c141e https://git.kernel.org/stable/c/f6a7c51cf07a399ec067d39f0a22f1817c5c7d2b https://git.kernel.org/stable/c/1f57f78fbacf630430bf954e5a84caafd •
CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2023-52872 – tty: n_gsm: fix race condition in status line change on dead connections
https://notcve.org/view.php?id=CVE-2023-52872
In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix race condition in status line change on dead connections gsm_cleanup_mux() cleans up the gsm by closing all DLCIs, stopping all timers, removing the virtual tty devices and clearing the data queues. This procedure, however, may cause subsequent changes of the virtual modem status lines of a DLCI. More data is being added the outgoing data queue and the deleted kick timer is restarted to handle this. At this point many resources have already been removed by the cleanup procedure. Thus, a kernel panic occurs. Fix this by proving in gsm_modem_update() that the cleanup procedure has not been started and the mux is still alive. Note that writing to a virtual tty is already protected by checks against the DLCI specific connection state. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: tty: n_gsm: corrige la condición de ejecución en la línea de estado, cambia en conexiones inactivas gsm_cleanup_mux() limpia el gsm cerrando todos los DLCI, deteniendo todos los temporizadores, eliminando los dispositivos tty virtuales y limpiando el colas de datos. • https://git.kernel.org/stable/c/dd37f657387853623f20c1b2482afbb9cd8ece33 https://git.kernel.org/stable/c/c568f7086c6e771c77aad13d727c70ef70e07243 https://git.kernel.org/stable/c/d834aba5f30d9a6f98f4ca1eb07e501f1989331c https://git.kernel.org/stable/c/692e847a8e6607909c4a3f98ab16ccee7849bd11 https://git.kernel.org/stable/c/81a4dd5e6c78f5d8952fa8c9d36565db1fe01444 https://git.kernel.org/stable/c/df6cfab66ff2a44bd23ad5dd5309cb3421bb6593 https://git.kernel.org/stable/c/19d34b73234af542cc8a218cf398dee73cdb1890 https://git.kernel.org/stable/c/ce4df90333c4fe65acb8b5089fdfe9b95 • CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') •
CVSS: -EPSS: 0%CPEs: 7EXPL: 0CVE-2023-52871 – soc: qcom: llcc: Handle a second device without data corruption
https://notcve.org/view.php?id=CVE-2023-52871
In the Linux kernel, the following vulnerability has been resolved: soc: qcom: llcc: Handle a second device without data corruption Usually there is only one llcc device. But if there were a second, even a failed probe call would modify the global drv_data pointer. So check if drv_data is valid before overwriting it. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: soc: qcom: llcc: Manejar un segundo dispositivo sin corrupción de datos. Generalmente solo hay un dispositivo llcc. • https://git.kernel.org/stable/c/a3134fb09e0bc5bee76e13bf863173b86f21cf87 https://git.kernel.org/stable/c/cc1a1dcb411fe224f48553cfdcdfe6e61395b69c https://git.kernel.org/stable/c/5e5b85ea0f4bc484bfe4cc73ead51fa48d2366a0 https://git.kernel.org/stable/c/995ee1e84e8db7fa5dcdde7dfe0bd7bb6f9bbb8c https://git.kernel.org/stable/c/f0ef883cae309bc5e8cdfcdbc1b4822732ce20a8 https://git.kernel.org/stable/c/3565684309e54fa998ea27f37028d67cc3e1dff2 https://git.kernel.org/stable/c/1143bfb9b055897975aeaea254da148e19524493 https://git.kernel.org/stable/c/f1a1bc8775b26345aba2be278118999e7 •
CVSS: 4.1EPSS: 0%CPEs: 6EXPL: 0CVE-2023-52870 – clk: mediatek: clk-mt6765: Add check for mtk_alloc_clk_data
https://notcve.org/view.php?id=CVE-2023-52870
In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: clk-mt6765: Add check for mtk_alloc_clk_data Add the check for the return value of mtk_alloc_clk_data() in order to avoid NULL pointer dereference. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: clk: mediatek: clk-mt6765: Agregar verificación para mtk_alloc_clk_data. Agregue la verificación para el valor de retorno de mtk_alloc_clk_data() para evitar la desreferencia al puntero NULL. • https://git.kernel.org/stable/c/1aca9939bf72893887cb7e3455e44c864bada2f9 https://git.kernel.org/stable/c/2617aa8ceaf30e41d3eb7f5fef3445542bef193a https://git.kernel.org/stable/c/533ca5153ad6c7b7d47ae0114b14d0333964b946 https://git.kernel.org/stable/c/dd1f30d68fa98eb672c0a259297b761656a9025f https://git.kernel.org/stable/c/10cc81124407d862f0f747db4baa9c006510b480 https://git.kernel.org/stable/c/b5ff3e89b4e7f46ad2aa0de7e08d18e6f87d71bc https://git.kernel.org/stable/c/b82681042724924ae3ba0f2f2eeec217fa31e830 • CWE-476: NULL Pointer Dereference •