Поиск уязвимостей
Количество 19
Количество 19
CVE-2024-45010
In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only mark 'subflow' endp as available Adding the following warning ... WARN_ON_ONCE(msk->pm.local_addr_used == 0) ... before decrementing the local_addr_used counter helped to find a bug when running the "remove single address" subtest from the mptcp_join.sh selftests. Removing a 'signal' endpoint will trigger the removal of all subflows linked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with rm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used counter, which is wrong in this case because this counter is linked to 'subflow' endpoints, and here it is a 'signal' endpoint that is being removed. Now, the counter is decremented, only if the ID is being used outside of mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and if the ID is not 0 -- local_addr_used is not taking into account these ones. This marking of the ID as being available, and the decrement is done no ...
CVE-2024-45010
In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only mark 'subflow' endp as available Adding the following warning ... WARN_ON_ONCE(msk->pm.local_addr_used == 0) ... before decrementing the local_addr_used counter helped to find a bug when running the "remove single address" subtest from the mptcp_join.sh selftests. Removing a 'signal' endpoint will trigger the removal of all subflows linked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with rm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used counter, which is wrong in this case because this counter is linked to 'subflow' endpoints, and here it is a 'signal' endpoint that is being removed. Now, the counter is decremented, only if the ID is being used outside of mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and if the ID is not 0 -- local_addr_used is not taking into account these ones. This marking of the ID as being available, and the decrement is done no ...
CVE-2024-45010
In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only mark 'subflow' endp as available Adding the following warning ... WARN_ON_ONCE(msk->pm.local_addr_used == 0) ... before decrementing the local_addr_used counter helped to find a bug when running the "remove single address" subtest from the mptcp_join.sh selftests. Removing a 'signal' endpoint will trigger the removal of all subflows linked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with rm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used counter, which is wrong in this case because this counter is linked to 'subflow' endpoints, and here it is a 'signal' endpoint that is being removed. Now, the counter is decremented, only if the ID is being used outside of mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and if the ID is not 0 -- local_addr_used is not taking into account these ones. This marking of the ID as being available, and the decrement is don
CVE-2024-45010
mptcp: pm: only mark 'subflow' endp as available
CVE-2024-45010
In the Linux kernel, the following vulnerability has been resolved: m ...
GHSA-mfw6-959v-265j
In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only mark 'subflow' endp as available Adding the following warning ... WARN_ON_ONCE(msk->pm.local_addr_used == 0) ... before decrementing the local_addr_used counter helped to find a bug when running the "remove single address" subtest from the mptcp_join.sh selftests. Removing a 'signal' endpoint will trigger the removal of all subflows linked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with rm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used counter, which is wrong in this case because this counter is linked to 'subflow' endpoints, and here it is a 'signal' endpoint that is being removed. Now, the counter is decremented, only if the ID is being used outside of mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and if the ID is not 0 -- local_addr_used is not taking into account these ones. This marking of the ID as being available, and the decrement is ...
BDU:2025-03751
Уязвимость функции mptcp_pm_nl_rm_addr_or_subflow() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260112-7385
Уязвимость kernel-lt
SUSE-SU-2025:0784-1
Security update for the Linux Kernel
SUSE-SU-2025:0955-1
Security update for the Linux Kernel
SUSE-SU-2025:0856-1
Security update for the Linux Kernel
SUSE-SU-2025:0847-1
Security update for the Linux Kernel
ALT-PU-2024-12970
ALT-PU-2024-12970: package `kernel-image-std-def` update to version 6.1.111-alt0.p11.1
ELSA-2025-6966
ELSA-2025-6966: kernel security update (MODERATE)
ALT-PU-2024-11855
ALT-PU-2024-11855: package `kernel-image-un-def` update to version 6.6.48-alt0.p11.1
ALT-PU-2024-13260
ALT-PU-2024-13260: package `kernel-image-pine` update to version 6.10.11-alt1
ALT-PU-2024-13121
ALT-PU-2024-13121: package `kernel-image-un-def` update to version 6.1.111-alt1
ALT-PU-2024-13979
ALT-PU-2024-13979: package `kernel-image-rpi-un` update to version 6.6.56-alt1
ALT-PU-2024-14046
ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-45010 In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only mark 'subflow' endp as available Adding the following warning ... WARN_ON_ONCE(msk->pm.local_addr_used == 0) ... before decrementing the local_addr_used counter helped to find a bug when running the "remove single address" subtest from the mptcp_join.sh selftests. Removing a 'signal' endpoint will trigger the removal of all subflows linked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with rm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used counter, which is wrong in this case because this counter is linked to 'subflow' endpoints, and here it is a 'signal' endpoint that is being removed. Now, the counter is decremented, only if the ID is being used outside of mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and if the ID is not 0 -- local_addr_used is not taking into account these ones. This marking of the ID as being available, and the decrement is done no ... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2024-45010 In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only mark 'subflow' endp as available Adding the following warning ... WARN_ON_ONCE(msk->pm.local_addr_used == 0) ... before decrementing the local_addr_used counter helped to find a bug when running the "remove single address" subtest from the mptcp_join.sh selftests. Removing a 'signal' endpoint will trigger the removal of all subflows linked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with rm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used counter, which is wrong in this case because this counter is linked to 'subflow' endpoints, and here it is a 'signal' endpoint that is being removed. Now, the counter is decremented, only if the ID is being used outside of mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and if the ID is not 0 -- local_addr_used is not taking into account these ones. This marking of the ID as being available, and the decrement is done no ... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2024-45010 In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only mark 'subflow' endp as available Adding the following warning ... WARN_ON_ONCE(msk->pm.local_addr_used == 0) ... before decrementing the local_addr_used counter helped to find a bug when running the "remove single address" subtest from the mptcp_join.sh selftests. Removing a 'signal' endpoint will trigger the removal of all subflows linked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with rm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used counter, which is wrong in this case because this counter is linked to 'subflow' endpoints, and here it is a 'signal' endpoint that is being removed. Now, the counter is decremented, only if the ID is being used outside of mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and if the ID is not 0 -- local_addr_used is not taking into account these ones. This marking of the ID as being available, and the decrement is don | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2024-45010 mptcp: pm: only mark 'subflow' endp as available | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2024-45010 In the Linux kernel, the following vulnerability has been resolved: m ... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
GHSA-mfw6-959v-265j In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only mark 'subflow' endp as available Adding the following warning ... WARN_ON_ONCE(msk->pm.local_addr_used == 0) ... before decrementing the local_addr_used counter helped to find a bug when running the "remove single address" subtest from the mptcp_join.sh selftests. Removing a 'signal' endpoint will trigger the removal of all subflows linked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with rm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used counter, which is wrong in this case because this counter is linked to 'subflow' endpoints, and here it is a 'signal' endpoint that is being removed. Now, the counter is decremented, only if the ID is being used outside of mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and if the ID is not 0 -- local_addr_used is not taking into account these ones. This marking of the ID as being available, and the decrement is ... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
BDU:2025-03751 Уязвимость функции mptcp_pm_nl_rm_addr_or_subflow() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
ROS-20260112-7385 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
SUSE-SU-2025:0784-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:0955-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:0856-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:0847-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2024-12970 ALT-PU-2024-12970: package `kernel-image-std-def` update to version 6.1.111-alt0.p11.1 | CVSS3: 8.8 | около 2 лет назад | ||
ELSA-2025-6966 ELSA-2025-6966: kernel security update (MODERATE) | больше 1 года назад | |||
ALT-PU-2024-11855 ALT-PU-2024-11855: package `kernel-image-un-def` update to version 6.6.48-alt0.p11.1 | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-13260 ALT-PU-2024-13260: package `kernel-image-pine` update to version 6.10.11-alt1 | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-13121 ALT-PU-2024-13121: package `kernel-image-un-def` update to version 6.1.111-alt1 | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-13979 ALT-PU-2024-13979: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 7.8 | около 2 лет назад | ||
ALT-PU-2024-14046 ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 9.8 | почти 2 года назад |
Уязвимостей на страницу