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

Уязвимость функции spin_lock_irqsave() модуля drivers/infiniband/sw/rdmavt/qp.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании

In the Linux kernel, the following vulnerability has been resolved: IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition The documentation of the function rvt_error_qp says both r_lock and s_lock need to be held when calling that function. It also asserts using lockdep that both of those locks are held. However, the commit I referenced in Fixes accidentally makes the call to rvt_error_qp in rvt_ruc_loopback no longer covered by r_lock. This results in the lockdep assertion failing and also possibly in a race condition.

In the Linux kernel, the following vulnerability has been resolved: IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition The documentation of the function rvt_error_qp says both r_lock and s_lock need to be held when calling that function. It also asserts using lockdep that both of those locks are held. However, the commit I referenced in Fixes accidentally makes the call to rvt_error_qp in rvt_ruc_loopback no longer covered by r_lock. This results in the lockdep assertion failing and also possibly in a race condition.

In the Linux kernel, the following vulnerability has been resolved: IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition The documentation of the function rvt_error_qp says both r_lock and s_lock need to be held when calling that function. It also asserts using lockdep that both of those locks are held. However, the commit I referenced in Fixes accidentally makes the call to rvt_error_qp in rvt_ruc_loopback no longer covered by r_lock. This results in the lockdep assertion failing and also possibly in a race condition.

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

In the Linux kernel, the following vulnerability has been resolved: IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition The documentation of the function rvt_error_qp says both r_lock and s_lock need to be held when calling that function. It also asserts using lockdep that both of those locks are held. However, the commit I referenced in Fixes accidentally makes the call to rvt_error_qp in rvt_ruc_loopback no longer covered by r_lock. This results in the lockdep assertion failing and also possibly in a race condition.

ALT-PU-2022-1735: package `kernel-image-std-def` update to version 5.10.111-alt1

ALT-PU-2022-7802: package `kernel-image-std-def` update to version 5.15.34-alt1

ALT-PU-2022-7696: package `kernel-image-un-def` update to version 5.15.34-alt1

ALT-PU-2022-1692: package `kernel-image-un-def` update to version 5.16.20-alt1

ALT-PU-2022-1830: package `kernel-image-rpi-def` update to version 5.15.36-alt1

ALT-PU-2022-1881: package `kernel-image-rt` update to version 5.10.115-alt1.rt67

ALT-PU-2022-1880: package `kernel-image-rt` update to version 5.10.115-alt1.rt67

ALT-PU-2022-1907: package `kernel-image-std-kvm` update to version 5.10.117-alt1

ALT-PU-2022-1730: package `kernel-image-mp` update to version 5.17.4-alt1

ALT-PU-2022-1833: package `kernel-image-rpi-def` update to version 5.15.36-alt1

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

ALT-PU-2022-2152: package `kernel-image-rpi-un` update to version 5.18.7-alt1

ALT-PU-2022-2155: package `kernel-image-rpi-un` update to version 5.18.7-alt1

Security update for the Linux Kernel