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

Уязвимость функции mlxreg_fan_set_cur_state() модуля drivers/hwmon/mlxreg-fan.c драйвера мониторинга оборудования ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании

In the Linux kernel, the following vulnerability has been resolved: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs Fan speed minimum can be enforced from sysfs. For example, setting current fan speed to 20 is used to enforce fan speed to be at 100% speed, 19 - to be not below 90% speed, etcetera. This feature provides ability to limit fan speed according to some system wise considerations, like absence of some replaceable units or high system ambient temperature. Request for changing fan minimum speed is configuration request and can be set only through 'sysfs' write procedure. In this situation value of argument 'state' is above nominal fan speed maximum. Return non-zero code in this case to avoid thermal_cooling_device_stats_update() call, because in this case statistics update violates thermal statistics table range. The issues is observed in case kernel is configured with option CONFIG_THERMAL_STATISTICS. Here is the trace from KASAN: [ ...

In the Linux kernel, the following vulnerability has been resolved: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs Fan speed minimum can be enforced from sysfs. For example, setting current fan speed to 20 is used to enforce fan speed to be at 100% speed, 19 - to be not below 90% speed, etcetera. This feature provides ability to limit fan speed according to some system wise considerations, like absence of some replaceable units or high system ambient temperature. Request for changing fan minimum speed is configuration request and can be set only through 'sysfs' write procedure. In this situation value of argument 'state' is above nominal fan speed maximum. Return non-zero code in this case to avoid thermal_cooling_device_stats_update() call, because in this case statistics update violates thermal statistics table range. The issues is observed in case kernel is configured with option CONFIG_THERMAL_STATISTICS. Here is the trace from KASAN: [ ...

In the Linux kernel, the following vulnerability has been resolved: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs Fan speed minimum can be enforced from sysfs. For example, setting current fan speed to 20 is used to enforce fan speed to be at 100% speed, 19 - to be not below 90% speed, etcetera. This feature provides ability to limit fan speed according to some system wise considerations, like absence of some replaceable units or high system ambient temperature. Request for changing fan minimum speed is configuration request and can be set only through 'sysfs' write procedure. In this situation value of argument 'state' is above nominal fan speed maximum. Return non-zero code in this case to avoid thermal_cooling_device_stats_update() call, because in this case statistics update violates thermal statistics table range. The issues is observed in case kernel is configured with option CONFIG_THERMAL_STATISTICS. Here is the trace from KASAN: [

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

In the Linux kernel, the following vulnerability has been resolved: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs Fan speed minimum can be enforced from sysfs. For example, setting current fan speed to 20 is used to enforce fan speed to be at 100% speed, 19 - to be not below 90% speed, etcetera. This feature provides ability to limit fan speed according to some system wise considerations, like absence of some replaceable units or high system ambient temperature. Request for changing fan minimum speed is configuration request and can be set only through 'sysfs' write procedure. In this situation value of argument 'state' is above nominal fan speed maximum. Return non-zero code in this case to avoid thermal_cooling_device_stats_update() call, because in this case statistics update violates thermal statistics table range. The issues is observed in case kernel is configured with option CONFIG_THERMAL_STATISTICS. Here is the trace from KASAN...

ALT-PU-2021-2989: package `kernel-image-std-def` update to version 5.10.71-alt1

ALT-PU-2021-2996: package `kernel-image-un-def` update to version 5.14.10-alt1

ALT-PU-2021-2998: package `kernel-image-std-kvm` update to version 5.10.71-alt1

ALT-PU-2021-3021: package `kernel-image-std-def` update to version 5.10.72-alt1

ALT-PU-2021-3055: package `kernel-image-rt` update to version 5.10.73-alt1.rt54

ALT-PU-2021-3035: package `kernel-image-mp` update to version 5.14.12-alt1

ALT-PU-2021-3067: package `kernel-image-un-def` update to version 5.14.13-alt1

ALT-PU-2021-3458: package `kernel-image-rpi-def` update to version 5.10.81-alt1

ALT-PU-2021-3451: package `kernel-image-rpi-def` update to version 5.10.81-alt1

ALT-PU-2021-3477: package `kernel-image-rt` update to version 5.10.78-alt1.rt56

ALT-PU-2022-7822: package `kernel-image-xenomai` update to version 4.19.229-alt1.cip67.21

ALT-PU-2022-2096: package `kernel-image-xenomai` update to version 4.19.229-alt1.cip67.21

ALT-PU-2021-3573: package `kernel-image-rpi-un` update to version 5.15.6-alt1

ALT-PU-2021-3563: package `kernel-image-rpi-un` update to version 5.15.6-alt1