CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-26823 – irqchip/gic-v3-its: Restore quirk probing for ACPI-based systems
https://notcve.org/view.php?id=CVE-2024-26823
In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Restore quirk probing for ACPI-based systems While refactoring the way the ITSs are probed, the handling of quirks applicable to ACPI-based platforms was lost. As a result, systems such as HIP07 lose their GICv4 functionnality, and some other may even fail to boot, unless they are configured to boot with DT. Move the enabling of quirks into its_probe_one(), making it common to all firmware implementations. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: irqchip/gic-v3-its: restaurar el sondeo de peculiaridades para sistemas basados en ACPI Al refactorizar la forma en que se sondean los ITS, se perdió el manejo de peculiaridades aplicables a plataformas basadas en ACPI. Como resultado, sistemas como HIP07 pierden su funcionalidad GICv4 y es posible que algunos otros incluso no arranquen, a menos que estén configurados para arrancar con DT. Mueva la habilitación de peculiaridades a its_probe_one(), haciéndola común a todas las implementaciones de firmware. • https://git.kernel.org/stable/c/9585a495ac936049dba141e8f9d99159ca06d46a https://git.kernel.org/stable/c/91a80fff3eeed928b6fba21271f6a9719b22a5d8 https://git.kernel.org/stable/c/4c60c611441f1f1e5de8e00e98ee5a4970778a00 https://git.kernel.org/stable/c/8b02da04ad978827e5ccd675acf170198f747a7a •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-26822 – smb: client: set correct id, uid and cruid for multiuser automounts
https://notcve.org/view.php?id=CVE-2024-26822
In the Linux kernel, the following vulnerability has been resolved: smb: client: set correct id, uid and cruid for multiuser automounts When uid, gid and cruid are not specified, we need to dynamically set them into the filesystem context used for automounting otherwise they'll end up reusing the values from the parent mount. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: smb: cliente: configure el id, uid y cruid correctos para montajes automáticos multiusuario Cuando no se especifican uid, gid y cruid, debemos configurarlos dinámicamente en el contexto del sistema de archivos utilizado para el montaje automático, de lo contrario terminarán reutilizando los valores del montaje principal. • https://git.kernel.org/stable/c/9fd29a5bae6e8f94b410374099a6fddb253d2d5f https://git.kernel.org/stable/c/c8117ac42303f7ae99bbe53e4952f7d147cca1fb https://git.kernel.org/stable/c/60e3318e3e900ba1ddfead937012b3432dfccc92 https://git.kernel.org/stable/c/c2aa2718cda2d56b4a551cb40043e9abc9684626 https://git.kernel.org/stable/c/7590ba9057c6d74c66f3b909a383ec47cd2f27fb https://git.kernel.org/stable/c/4508ec17357094e2075f334948393ddedbb75157 •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-26820 – hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed
https://notcve.org/view.php?id=CVE-2024-26820
In the Linux kernel, the following vulnerability has been resolved: hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed If hv_netvsc driver is unloaded and reloaded, the NET_DEVICE_REGISTER handler cannot perform VF register successfully as the register call is received before netvsc_probe is finished. This is because we register register_netdevice_notifier() very early( even before vmbus_driver_register()). To fix this, we try to register each such matching VF( if it is visible as a netdevice) at the end of netvsc_probe. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: hv_netvsc: registre VF en netvsc_probe si se perdió NET_DEVICE_REGISTER. Si el controlador hv_netvsc se descarga y se vuelve a cargar, el controlador NET_DEVICE_REGISTER no puede realizar el registro VF exitosamente ya que la llamada de registro se recibe antes de que finalice netvsc_probe. Esto se debe a que registramos Register_netdevice_notifier() muy temprano (incluso antes de vmbus_driver_register()). • https://git.kernel.org/stable/c/028aa21f9e92536038cabb834c15d08f5c894382 https://git.kernel.org/stable/c/997d895fa495fb3421983923219bba93f1a793ee https://git.kernel.org/stable/c/ff6c130e48a79c826cbc2427bd8b34a7592460cc https://git.kernel.org/stable/c/97683466e24c801ee4e865ce90ac7e355db2da59 https://git.kernel.org/stable/c/5dd83db613be8e5c5d30efed7f42780e9eb18380 https://git.kernel.org/stable/c/7350c460f7f48a8653a15c5c90fc9070aaa29535 https://git.kernel.org/stable/c/85520856466ed6bc3b1ccb013cddac70ceb437db https://git.kernel.org/stable/c/bcb7164258d0a9a8aa2e73ddccc2d78f6 •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-26818 – tools/rtla: Fix clang warning about mount_point var size
https://notcve.org/view.php?id=CVE-2024-26818
In the Linux kernel, the following vulnerability has been resolved: tools/rtla: Fix clang warning about mount_point var size clang is reporting this warning: $ make HOSTCC=clang CC=clang LLVM_IAS=1 [...] clang -O -g -DVERSION=\"6.8.0-rc3\" -flto=auto -fexceptions -fstack-protector-strong -fasynchronous-unwind-tables -fstack-clash-protection -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS $(pkg-config --cflags libtracefs) -c -o src/utils.o src/utils.c src/utils.c:548:66: warning: 'fscanf' may overflow; destination buffer in argument 3 has size 1024, but the corresponding specifier may require size 1025 [-Wfortify-source] 548 | while (fscanf(fp, "%*s %" STR(MAX_PATH) "s %99s %*s %*d %*d\n", mount_point, type) == 2) { | ^ Increase mount_point variable size to MAX_PATH+1 to avoid the overflow. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: herramientas/rtla: Repare la advertencia de clang sobre el tamaño de var de mount_point clang informa esta advertencia: $ make HOSTCC=clang CC=clang LLVM_IAS=1 [...] clang -O -g -DVERSION=\"6.8.0-rc3\" -flto=auto -fExceptions -fstack-protector-strong -fasynchronous-unwind-tables -fstack-clash-protection -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE= 2 -Wp,-D_GLIBCXX_ASSERTIONS $(pkg-config --cflags libtracefs) -c -o src/utils.o src/utils.c src/utils.c:548:66: advertencia: 'fscanf' puede desbordarse; el búfer de destino en el argumento 3 tiene un tamaño 1024, pero el especificador correspondiente puede requerir un tamaño 1025 [-Wfortify-source] 548 | while (fscanf(fp, "%*s %" STR(MAX_PATH) "s %99s %*s %*d %*d\n", punto_montaje, tipo) == 2) { | ^ Aumente el tamaño de la variable mount_point a MAX_PATH+1 para evitar el desbordamiento. • https://git.kernel.org/stable/c/a957cbc02531a23beeac6dd9e751f8d4dadaf7a9 https://git.kernel.org/stable/c/8a585914c266dc044f53b5c83c170f79b45fcf9a https://git.kernel.org/stable/c/6bdd43f62ab3bb5a306af7f0ab857af45777f5a8 https://git.kernel.org/stable/c/30369084ac6e27479a347899e74f523e6ca29b89 •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2023-52643 – iio: core: fix memleak in iio_device_register_sysfs
https://notcve.org/view.php?id=CVE-2023-52643
In the Linux kernel, the following vulnerability has been resolved: iio: core: fix memleak in iio_device_register_sysfs When iio_device_register_sysfs_group() fails, we should free iio_dev_opaque->chan_attr_group.attrs to prevent potential memleak. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: iio: core: corrige memleak en iio_device_register_sysfs Cuando falla iio_device_register_sysfs_group(), debemos liberar iio_dev_opaque->chan_attr_group.attrs para evitar posibles fugas de mem. • https://git.kernel.org/stable/c/32f171724e5cbecc80594fb6eced057cfdd6eb6f https://git.kernel.org/stable/c/1c6d19c8cbf6abcea2c8fca2db26abca2cbf0363 https://git.kernel.org/stable/c/359f220d0e753bba840eac19ffedcdc816b532f2 https://git.kernel.org/stable/c/b90126c86d83912688501826643ea698f0df1728 https://git.kernel.org/stable/c/3db312e06851996e7fb27cb5a8ccab4c0f9cdb93 https://git.kernel.org/stable/c/95a0d596bbd0552a78e13ced43f2be1038883c81 •