Поиск уязвимостей
Количество 26
Количество 26
CVE-2024-35910
In the Linux kernel, the following vulnerability has been resolved: tcp: properly terminate timers for kernel sockets We had various syzbot reports about tcp timers firing after the corresponding netns has been dismantled. Fortunately Josef Bacik could trigger the issue more often, and could test a patch I wrote two years ago. When TCP sockets are closed, we call inet_csk_clear_xmit_timers() to 'stop' the timers. inet_csk_clear_xmit_timers() can be called from any context, including when socket lock is held. This is the reason it uses sk_stop_timer(), aka del_timer(). This means that ongoing timers might finish much later. For user sockets, this is fine because each running timer holds a reference on the socket, and the user socket holds a reference on the netns. For kernel sockets, we risk that the netns is freed before timer can complete, because kernel sockets do not hold reference on the netns. This patch adds inet_csk_clear_xmit_timers_sync() function that using sk_stop_timer_s...
CVE-2024-35910
In the Linux kernel, the following vulnerability has been resolved: tcp: properly terminate timers for kernel sockets We had various syzbot reports about tcp timers firing after the corresponding netns has been dismantled. Fortunately Josef Bacik could trigger the issue more often, and could test a patch I wrote two years ago. When TCP sockets are closed, we call inet_csk_clear_xmit_timers() to 'stop' the timers. inet_csk_clear_xmit_timers() can be called from any context, including when socket lock is held. This is the reason it uses sk_stop_timer(), aka del_timer(). This means that ongoing timers might finish much later. For user sockets, this is fine because each running timer holds a reference on the socket, and the user socket holds a reference on the netns. For kernel sockets, we risk that the netns is freed before timer can complete, because kernel sockets do not hold reference on the netns. This patch adds inet_csk_clear_xmit_timers_sync() function that using sk_stop_timer_s...
CVE-2024-35910
In the Linux kernel, the following vulnerability has been resolved: tcp: properly terminate timers for kernel sockets We had various syzbot reports about tcp timers firing after the corresponding netns has been dismantled. Fortunately Josef Bacik could trigger the issue more often, and could test a patch I wrote two years ago. When TCP sockets are closed, we call inet_csk_clear_xmit_timers() to 'stop' the timers. inet_csk_clear_xmit_timers() can be called from any context, including when socket lock is held. This is the reason it uses sk_stop_timer(), aka del_timer(). This means that ongoing timers might finish much later. For user sockets, this is fine because each running timer holds a reference on the socket, and the user socket holds a reference on the netns. For kernel sockets, we risk that the netns is freed before timer can complete, because kernel sockets do not hold reference on the netns. This patch adds inet_csk_clear_xmit_timers_sync() function that using sk_stop_ti
CVE-2024-35910
In the Linux kernel, the following vulnerability has been resolved: t ...
GHSA-f8qw-j52x-qgrm
In the Linux kernel, the following vulnerability has been resolved: tcp: properly terminate timers for kernel sockets We had various syzbot reports about tcp timers firing after the corresponding netns has been dismantled. Fortunately Josef Bacik could trigger the issue more often, and could test a patch I wrote two years ago. When TCP sockets are closed, we call inet_csk_clear_xmit_timers() to 'stop' the timers. inet_csk_clear_xmit_timers() can be called from any context, including when socket lock is held. This is the reason it uses sk_stop_timer(), aka del_timer(). This means that ongoing timers might finish much later. For user sockets, this is fine because each running timer holds a reference on the socket, and the user socket holds a reference on the netns. For kernel sockets, we risk that the netns is freed before timer can complete, because kernel sockets do not hold reference on the netns. This patch adds inet_csk_clear_xmit_timers_sync() function that using sk_stop...
BDU:2024-09897
Уязвимость компонента tcp ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20241114-01
Множественные уязвимости kernel-lt
ALT-PU-2024-18367
ALT-PU-2024-18367: package `kernel-image-std-def` update to version 6.1.85-alt1
ALT-PU-2024-18060
ALT-PU-2024-18060: package `kernel-image-un-def` update to version 6.1.85-alt1
ALT-PU-2024-18471
ALT-PU-2024-18471: package `kernel-image-un-def` update to version 6.6.26-alt1
ALT-PU-2024-18144
ALT-PU-2024-18144: package `kernel-image-6.8` update to version 6.8.5-alt1
RLSA-2024:5101
Important: kernel security update
ELSA-2024-5101
ELSA-2024-5101: kernel security update (IMPORTANT)
SUSE-SU-2025:1177-1
Security update for the Linux Kernel
SUSE-SU-2025:1180-1
Security update for the Linux Kernel
SUSE-SU-2025:1178-1
Security update for the Linux Kernel
SUSE-SU-2025:1293-1
Security update for the Linux Kernel
ALT-PU-2024-18077
ALT-PU-2024-18077: package `kernel-image-rt` update to version 5.10.215-alt1.rt107
SUSE-SU-2025:01951-1
Security update for the Linux Kernel
SUSE-SU-2025:01967-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-35910 In the Linux kernel, the following vulnerability has been resolved: tcp: properly terminate timers for kernel sockets We had various syzbot reports about tcp timers firing after the corresponding netns has been dismantled. Fortunately Josef Bacik could trigger the issue more often, and could test a patch I wrote two years ago. When TCP sockets are closed, we call inet_csk_clear_xmit_timers() to 'stop' the timers. inet_csk_clear_xmit_timers() can be called from any context, including when socket lock is held. This is the reason it uses sk_stop_timer(), aka del_timer(). This means that ongoing timers might finish much later. For user sockets, this is fine because each running timer holds a reference on the socket, and the user socket holds a reference on the netns. For kernel sockets, we risk that the netns is freed before timer can complete, because kernel sockets do not hold reference on the netns. This patch adds inet_csk_clear_xmit_timers_sync() function that using sk_stop_timer_s... | CVSS3: 5.8 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35910 In the Linux kernel, the following vulnerability has been resolved: tcp: properly terminate timers for kernel sockets We had various syzbot reports about tcp timers firing after the corresponding netns has been dismantled. Fortunately Josef Bacik could trigger the issue more often, and could test a patch I wrote two years ago. When TCP sockets are closed, we call inet_csk_clear_xmit_timers() to 'stop' the timers. inet_csk_clear_xmit_timers() can be called from any context, including when socket lock is held. This is the reason it uses sk_stop_timer(), aka del_timer(). This means that ongoing timers might finish much later. For user sockets, this is fine because each running timer holds a reference on the socket, and the user socket holds a reference on the netns. For kernel sockets, we risk that the netns is freed before timer can complete, because kernel sockets do not hold reference on the netns. This patch adds inet_csk_clear_xmit_timers_sync() function that using sk_stop_timer_s... | CVSS3: 5.8 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35910 In the Linux kernel, the following vulnerability has been resolved: tcp: properly terminate timers for kernel sockets We had various syzbot reports about tcp timers firing after the corresponding netns has been dismantled. Fortunately Josef Bacik could trigger the issue more often, and could test a patch I wrote two years ago. When TCP sockets are closed, we call inet_csk_clear_xmit_timers() to 'stop' the timers. inet_csk_clear_xmit_timers() can be called from any context, including when socket lock is held. This is the reason it uses sk_stop_timer(), aka del_timer(). This means that ongoing timers might finish much later. For user sockets, this is fine because each running timer holds a reference on the socket, and the user socket holds a reference on the netns. For kernel sockets, we risk that the netns is freed before timer can complete, because kernel sockets do not hold reference on the netns. This patch adds inet_csk_clear_xmit_timers_sync() function that using sk_stop_ti | CVSS3: 5.8 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35910 In the Linux kernel, the following vulnerability has been resolved: t ... | CVSS3: 5.8 | 0% Низкий | больше 2 лет назад | |
GHSA-f8qw-j52x-qgrm In the Linux kernel, the following vulnerability has been resolved: tcp: properly terminate timers for kernel sockets We had various syzbot reports about tcp timers firing after the corresponding netns has been dismantled. Fortunately Josef Bacik could trigger the issue more often, and could test a patch I wrote two years ago. When TCP sockets are closed, we call inet_csk_clear_xmit_timers() to 'stop' the timers. inet_csk_clear_xmit_timers() can be called from any context, including when socket lock is held. This is the reason it uses sk_stop_timer(), aka del_timer(). This means that ongoing timers might finish much later. For user sockets, this is fine because each running timer holds a reference on the socket, and the user socket holds a reference on the netns. For kernel sockets, we risk that the netns is freed before timer can complete, because kernel sockets do not hold reference on the netns. This patch adds inet_csk_clear_xmit_timers_sync() function that using sk_stop... | CVSS3: 5.8 | 0% Низкий | больше 2 лет назад | |
BDU:2024-09897 Уязвимость компонента tcp ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
ROS-20241114-01 Множественные уязвимости kernel-lt | CVSS3: 8.8 | почти 2 года назад | ||
ALT-PU-2024-18367 ALT-PU-2024-18367: package `kernel-image-std-def` update to version 6.1.85-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18060 ALT-PU-2024-18060: package `kernel-image-un-def` update to version 6.1.85-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18471 ALT-PU-2024-18471: package `kernel-image-un-def` update to version 6.6.26-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18144 ALT-PU-2024-18144: package `kernel-image-6.8` update to version 6.8.5-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
RLSA-2024:5101 Important: kernel security update | около 2 лет назад | |||
ELSA-2024-5101 ELSA-2024-5101: kernel security update (IMPORTANT) | больше 2 лет назад | |||
SUSE-SU-2025:1177-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:1180-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:1178-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:1293-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2024-18077 ALT-PU-2024-18077: package `kernel-image-rt` update to version 5.10.215-alt1.rt107 | CVSS3: 9.1 | больше 2 лет назад | ||
SUSE-SU-2025:01951-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01967-1 Security update for the Linux Kernel | больше 1 года назад |
Уязвимостей на страницу