Page 377 of 4150 results (0.013 seconds)

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

In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: Assign dummy when codec not specified for a DAI link MediaTek sound card drivers are checking whether a DAI link is present and used on a board to assign the correct parameters and this is done by checking the codec DAI names at probe time. If no real codec is present, assign the dummy codec to the DAI link to avoid NULL pointer during string comparison. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ASoC: mediatek: Asignar dummy cuando el códec no está especificado para un enlace DAI Los controladores de la tarjeta de sonido MediaTek están comprobando si hay un enlace DAI presente y utilizado en una placa para asignar los parámetros correctos y esto se realiza comprobando los nombres DAI del códec en el momento de la sonda. Si no hay ningún códec real, asigne el códec ficticio al enlace DAI para evitar el puntero NULL durante la comparación de cadenas. • https://git.kernel.org/stable/c/4302187d955f166c03b4fa7c993b89ffbabfca4e https://git.kernel.org/stable/c/87b8dca6e06f9b1681bc52bf7bfa85c663a11158 https://git.kernel.org/stable/c/cbbcabc7f0979f6542372cf88d7a9da7143a4226 https://git.kernel.org/stable/c/0c052b1c11d8119f3048b1f7b3c39a90500cacf9 https://git.kernel.org/stable/c/5f39231888c63f0a7708abc86b51b847476379d8 •

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

In the Linux kernel, the following vulnerability has been resolved: ASoC: kirkwood: Fix potential NULL dereference In kirkwood_dma_hw_params() mv_mbus_dram_info() returns NULL if CONFIG_PLAT_ORION macro is not defined. Fix this bug by adding NULL check. Found by Linux Verification Center (linuxtesting.org) with SVACE. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: ASoC: kirkwood: corrige una posible desreferencia NULL En kirkwood_dma_hw_params() mv_mbus_dram_info() devuelve NULL si la macro CONFIG_PLAT_ORION no está definida. Corrija este error agregando una verificación NULL. Encontrado por el Centro de verificación de Linux (linuxtesting.org) con SVACE. • https://git.kernel.org/stable/c/bb6a40fc5a830cae45ddd5cd6cfa151b008522ed https://git.kernel.org/stable/c/145951900b763dc32bf31bd770f3f036a8348424 https://git.kernel.org/stable/c/d48d0c5fd733bd6d8d3ddb2ed553777ab4724169 https://git.kernel.org/stable/c/de9987cec6fde1dd41dfcb971433e05945852489 https://git.kernel.org/stable/c/1a7254525ca7a6f3e37d7882d7f7ad97f6235f7c https://git.kernel.org/stable/c/5bf5154739cd676b6d0958079070557c8d96afb6 https://git.kernel.org/stable/c/802b49e39da669b54bd9b77dc3c649999a446bf6 https://git.kernel.org/stable/c/ea60ab95723f5738e7737b56dda95e6fe • CWE-476: NULL Pointer Dereference •

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

In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Add 0 size check to mtk_drm_gem_obj Add a check to mtk_drm_gem_init if we attempt to allocate a GEM object of 0 bytes. Currently, no such check exists and the kernel will panic if a userspace application attempts to allocate a 0x0 GBM buffer. Tested by attempting to allocate a 0x0 GBM buffer on an MT8188 and verifying that we now return EINVAL. En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: drm/mediatek: Agregar verificación de tamaño 0 a mtk_drm_gem_obj Agregar una verificación a mtk_drm_gem_init si intentamos asignar un objeto GEM de 0 bytes. Actualmente, no existe tal verificación y el kernel entrará en pánico si una aplicación de espacio de usuario intenta asignar un búfer GBM 0x0. Probado intentando asignar un búfer GBM 0x0 en un MT8188 y verificando que ahora devolvemos EINVAL. • https://git.kernel.org/stable/c/119f5173628aa7a0c3cf9db83460d40709e8241d https://git.kernel.org/stable/c/79078880795478d551a05acc41f957700030d364 https://git.kernel.org/stable/c/be34a1b351ea7faeb15dde8c44fe89de3980ae67 https://git.kernel.org/stable/c/d17b75ee9c2e44d3a3682c4ea5ab713ea6073350 https://git.kernel.org/stable/c/0e3b6f9123726858cac299e1654e3d20424cabe4 https://git.kernel.org/stable/c/13562c2d48c9ee330de1077d00146742be368f05 https://git.kernel.org/stable/c/af26ea99019caee1500bf7e60c861136c0bf8594 https://git.kernel.org/stable/c/9489951e3ae505534c4013db4e76b1b5a •

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

In the Linux kernel, the following vulnerability has been resolved: drm: bridge: cdns-mhdp8546: Fix possible null pointer dereference In cdns_mhdp_atomic_enable(), the return value of drm_mode_duplicate() is assigned to mhdp_state->current_mode, and there is a dereference of it in drm_mode_set_name(), which will lead to a NULL pointer dereference on failure of drm_mode_duplicate(). Fix this bug add a check of mhdp_state->current_mode. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm: bridge: cdns-mhdp8546: corrige posible desreferencia del puntero nulo En cdns_mhdp_atomic_enable(), el valor de retorno de drm_mode_duplicate() se asigna a mhdp_state->current_mode, y hay una desreferencia de él en drm_mode_set_name(), lo que conducirá a una desreferencia del puntero NULL en caso de falla de drm_mode_duplicate(). Solucione este error y agregue una verificación de mhdp_state->current_mode. • https://git.kernel.org/stable/c/fb43aa0acdfd600c75b8c877bdf9f6e9893ffc9b https://git.kernel.org/stable/c/85d1a27402f81f2e04b0e67d20f749c2a14edbb3 https://git.kernel.org/stable/c/89788cd9824c28ffcdea40232c458233353d1896 https://git.kernel.org/stable/c/ca53b7efd4ba6ae92fd2b3085cb099c745e96965 https://git.kernel.org/stable/c/dcf53e6103b26e7458be71491d0641f49fbd5840 https://git.kernel.org/stable/c/32fb2ef124c3301656ac6c789a2ef35ef69a66da https://git.kernel.org/stable/c/47889711da20be9b43e1e136e5cb68df37cbcc79 https://git.kernel.org/stable/c/935a92a1c400285545198ca2800a4c6c5 • CWE-476: NULL Pointer Dereference •

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

In the Linux kernel, the following vulnerability has been resolved: media: atomisp: ssh_css: Fix a null-pointer dereference in load_video_binaries The allocation failure of mycs->yuv_scaler_binary in load_video_binaries() is followed with a dereference of mycs->yuv_scaler_binary after the following call chain: sh_css_pipe_load_binaries() |-> load_video_binaries(mycs->yuv_scaler_binary == NULL) | |-> sh_css_pipe_unload_binaries() |-> unload_video_binaries() In unload_video_binaries(), it calls to ia_css_binary_unload with argument &pipe->pipe_settings.video.yuv_scaler_binary[i], which refers to the same memory slot as mycs->yuv_scaler_binary. Thus, a null-pointer dereference is triggered. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: media: atomisp: ssh_css: corrige una desreferencia de puntero nulo en load_video_binaries La falla de asignación de mycs->yuv_scaler_binary en load_video_binaries() va seguida de una desreferencia de mycs->yuv_scaler_binary después de siguiente cadena de llamadas: sh_css_pipe_load_binaries() |-> load_video_binaries(mycs->yuv_scaler_binary == NULL) | |-> sh_css_pipe_unload_binaries() |-> unload_video_binaries() En unload_video_binaries(), llama a ia_css_binary_unload con el argumento &pipe->pipe_settings.video.yuv_scaler_binary[i], que se refiere a la misma ranura de memoria que mycs->yuv_scaler_binary. Por lo tanto, se activa una desreferencia de puntero nulo. • https://git.kernel.org/stable/c/a49d25364dfb9f8a64037488a39ab1f56c5fa419 https://git.kernel.org/stable/c/4b68b861b514a5c09220d622ac3784c0ebac6c80 https://git.kernel.org/stable/c/82c2c85aead3ea3cbceef4be077cf459c5df2272 https://git.kernel.org/stable/c/a1ab99dcc8604afe7e3bccb01b10da03bdd7ea35 https://git.kernel.org/stable/c/cc20c87b04db86c8e3e810bcdca686b406206069 https://git.kernel.org/stable/c/69b27ff82f87379afeaaea4b2f339032fdd8486e https://git.kernel.org/stable/c/6482c433863b257b0b9b687c28ce80b89d5f89f0 https://git.kernel.org/stable/c/3b621e9e9e148c0928ab109ac3d4b8148 •