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 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2023-52869 – pstore/platform: Add check for kstrdup
https://notcve.org/view.php?id=CVE-2023-52869
In the Linux kernel, the following vulnerability has been resolved: pstore/platform: Add check for kstrdup Add check for the return value of kstrdup() and return the error if it fails in order to avoid NULL pointer dereference. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: pstore/platform: Agregar verificación para kstrdup. Agregue verificación para el valor de retorno de kstrdup() y devuelva el error si falla para evitar la desreferencia del puntero NULL. • https://git.kernel.org/stable/c/563ca40ddf400dbf8c6254077f9b6887101d0f08 https://git.kernel.org/stable/c/bb166bdae1a7d7db30e9be7e6ccaba606debc05f https://git.kernel.org/stable/c/379b120e4f27fd1cf636a5f85570c4d240a3f688 https://git.kernel.org/stable/c/63f637309baadf81a095f2653e3b807d4b5814b9 https://git.kernel.org/stable/c/1c426da79f9fc7b761021b5eb44185ba119cd44a https://git.kernel.org/stable/c/ad5cb6deb41417ef41b9d6ff54f789212108606f https://git.kernel.org/stable/c/a19d48f7c5d57c0f0405a7d4334d1d38fe9d3c1c • CWE-476: NULL Pointer Dereference •
CVSS: -EPSS: 0%CPEs: 9EXPL: 0CVE-2023-52868 – thermal: core: prevent potential string overflow
https://notcve.org/view.php?id=CVE-2023-52868
In the Linux kernel, the following vulnerability has been resolved: thermal: core: prevent potential string overflow The dev->id value comes from ida_alloc() so it's a number between zero and INT_MAX. If it's too high then these sprintf()s will overflow. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: térmica: núcleo: evita un posible desbordamiento de cadenas. El valor dev->id proviene de ida_alloc(), por lo que es un número entre cero e INT_MAX. Si es demasiado alto, estos sprintf()s se desbordarán. • https://git.kernel.org/stable/c/203d3d4aa482339b4816f131f713e1b8ee37f6dd https://git.kernel.org/stable/c/b55f0a9f865be75ca1019aad331f3225f7b50ce8 https://git.kernel.org/stable/c/6ad1bf47fbe5750c4d5d8e41337665e193e2c521 https://git.kernel.org/stable/c/3091ab943dfc7b2578599b0fe203350286fab5bb https://git.kernel.org/stable/c/3f795fb35c2d8a637efe76b4518216c9319b998c https://git.kernel.org/stable/c/3a8f4e58e1ee707b4f46a1000b40b86ea3dd509c https://git.kernel.org/stable/c/77ff34a56b695e228e6daf30ee30be747973d6e8 https://git.kernel.org/stable/c/0f6b3be28c4d62ef6498133959c722666 •