Поиск уязвимостей

In the Linux kernel, the following vulnerability has been resolved: net: phy: fix phy_get_internal_delay accessing an empty array The phy_get_internal_delay function could try to access to an empty array in the case that the driver is calling phy_get_internal_delay without defining delay_values and rx-internal-delay-ps or tx-internal-delay-ps is defined to 0 in the device-tree. This will lead to "unable to handle kernel NULL pointer dereference at virtual address 0". To avoid this kernel oops, the test should be delay >= 0. As there is already delay < 0 test just before, the test could only be size == 0.

In the Linux kernel, the following vulnerability has been resolved: net: phy: fix phy_get_internal_delay accessing an empty array The phy_get_internal_delay function could try to access to an empty array in the case that the driver is calling phy_get_internal_delay without defining delay_values and rx-internal-delay-ps or tx-internal-delay-ps is defined to 0 in the device-tree. This will lead to "unable to handle kernel NULL pointer dereference at virtual address 0". To avoid this kernel oops, the test should be delay >= 0. As there is already delay < 0 test just before, the test could only be size == 0.

In the Linux kernel, the following vulnerability has been resolved: net: phy: fix phy_get_internal_delay accessing an empty array The phy_get_internal_delay function could try to access to an empty array in the case that the driver is calling phy_get_internal_delay without defining delay_values and rx-internal-delay-ps or tx-internal-delay-ps is defined to 0 in the device-tree. This will lead to "unable to handle kernel NULL pointer dereference at virtual address 0". To avoid this kernel oops, the test should be delay >= 0. As there is already delay < 0 test just before, the test could only be size == 0.

net: phy: fix phy_get_internal_delay accessing an empty array

In the Linux kernel, the following vulnerability has been resolved: n ...

In the Linux kernel, the following vulnerability has been resolved: net: phy: fix phy_get_internal_delay accessing an empty array The phy_get_internal_delay function could try to access to an empty array in the case that the driver is calling phy_get_internal_delay without defining delay_values and rx-internal-delay-ps or tx-internal-delay-ps is defined to 0 in the device-tree. This will lead to "unable to handle kernel NULL pointer dereference at virtual address 0". To avoid this kernel oops, the test should be delay >= 0. As there is already delay < 0 test just before, the test could only be size == 0.

Уязвимость компонента phy ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании

Множественные уязвимости kernel-lt

ALT-PU-2024-18365: package `kernel-image-std-def` update to version 6.1.83-alt1

ALT-PU-2024-18257: package `kernel-image-rt` update to version 6.1.83-alt1.rt28

ALT-PU-2024-18058: package `kernel-image-un-def` update to version 6.1.83-alt1

ALT-PU-2024-18469: package `kernel-image-un-def` update to version 6.6.23-alt1

ALT-PU-2024-18211: package `kernel-image-pine` update to version 6.6.23-alt1

ALT-PU-2024-18141: package `kernel-image-6.8` update to version 6.8.2-alt1

ALT-PU-2024-18077: package `kernel-image-rt` update to version 5.10.215-alt1.rt107

ALT-PU-2024-7511: package `kernel-image-std-def` update to version 5.10.216-alt1

Security update for the Linux Kernel

Security update for the Linux Kernel

ALT-PU-2024-18117: package `kernel-image-mp` update to version 6.7.12-alt1

Security update for the Linux Kernel