Количество 24
Количество 24
CVE-2026-43050
In the Linux kernel, the following vulnerability has been resolved: atm: lec: fix use-after-free in sock_def_readable() A race condition exists between lec_atm_close() setting priv->lecd to NULL and concurrent access to priv->lecd in send_to_lecd(), lec_handle_bridge(), and lec_atm_send(). When the socket is freed via RCU while another thread is still using it, a use-after-free occurs in sock_def_readable() when accessing the socket's wait queue. The root cause is that lec_atm_close() clears priv->lecd without any synchronization, while callers dereference priv->lecd without any protection against concurrent teardown. Fix this by converting priv->lecd to an RCU-protected pointer: - Mark priv->lecd as __rcu in lec.h - Use rcu_assign_pointer() in lec_atm_close() and lecd_attach() for safe pointer assignment - Use rcu_access_pointer() for NULL checks that do not dereference the pointer in lec_start_xmit(), lec_push(), send_to_lecd() and lecd_attach() - Use rcu_read_lock/rcu_dereference...
CVE-2026-43050
In the Linux kernel, the following vulnerability has been resolved: atm: lec: fix use-after-free in sock_def_readable() A race condition exists between lec_atm_close() setting priv->lecd to NULL and concurrent access to priv->lecd in send_to_lecd(), lec_handle_bridge(), and lec_atm_send(). When the socket is freed via RCU while another thread is still using it, a use-after-free occurs in sock_def_readable() when accessing the socket's wait queue. The root cause is that lec_atm_close() clears priv->lecd without any synchronization, while callers dereference priv->lecd without any protection against concurrent teardown. Fix this by converting priv->lecd to an RCU-protected pointer: - Mark priv->lecd as __rcu in lec.h - Use rcu_assign_pointer() in lec_atm_close() and lecd_attach() for safe pointer assignment - Use rcu_access_pointer() for NULL checks that do not dereference the pointer in lec_start_xmit(), lec_push(), send_to_lecd() and lecd_attach() - Use rcu_read_lock/rcu_dereference...
CVE-2026-43050
In the Linux kernel, the following vulnerability has been resolved: atm: lec: fix use-after-free in sock_def_readable() A race condition exists between lec_atm_close() setting priv->lecd to NULL and concurrent access to priv->lecd in send_to_lecd(), lec_handle_bridge(), and lec_atm_send(). When the socket is freed via RCU while another thread is still using it, a use-after-free occurs in sock_def_readable() when accessing the socket's wait queue. The root cause is that lec_atm_close() clears priv->lecd without any synchronization, while callers dereference priv->lecd without any protection against concurrent teardown. Fix this by converting priv->lecd to an RCU-protected pointer: - Mark priv->lecd as __rcu in lec.h - Use rcu_assign_pointer() in lec_atm_close() and lecd_attach() for safe pointer assignment - Use rcu_access_pointer() for NULL checks that do not dereference the pointer in lec_start_xmit(), lec_push(), send_to_lecd() and lecd_attach() - Use rcu_read_lock/rcu_dere
CVE-2026-43050
In the Linux kernel, the following vulnerability has been resolved: a ...
GHSA-jhj6-5p6x-hw75
In the Linux kernel, the following vulnerability has been resolved: atm: lec: fix use-after-free in sock_def_readable() A race condition exists between lec_atm_close() setting priv->lecd to NULL and concurrent access to priv->lecd in send_to_lecd(), lec_handle_bridge(), and lec_atm_send(). When the socket is freed via RCU while another thread is still using it, a use-after-free occurs in sock_def_readable() when accessing the socket's wait queue. The root cause is that lec_atm_close() clears priv->lecd without any synchronization, while callers dereference priv->lecd without any protection against concurrent teardown. Fix this by converting priv->lecd to an RCU-protected pointer: - Mark priv->lecd as __rcu in lec.h - Use rcu_assign_pointer() in lec_atm_close() and lecd_attach() for safe pointer assignment - Use rcu_access_pointer() for NULL checks that do not dereference the pointer in lec_start_xmit(), lec_push(), send_to_lecd() and lecd_attach() - Use rcu_read_lock/rcu_d...
BDU:2026-07835
Уязвимость функции sock_def_readable() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260918-80-0029
Уязвимость kernel-lt
ROS-20260918-73-0027
Уязвимость kernel-lt
SUSE-SU-2026:2202-1
Security update for the Linux Kernel
SUSE-SU-2026:2215-1
Security update for the Linux Kernel
SUSE-SU-2026:2195-1
Security update for the Linux Kernel
SUSE-SU-2026:2217-1
Security update for the Linux Kernel
SUSE-SU-2026:2238-1
Security update for the Linux Kernel
openSUSE-SU-2026:20826-1
Security update for the Linux Kernel
ALT-PU-2026-6805
ALT-PU-2026-6805: package `kernel-image-un-def` update to version 6.1.168-alt1
ALT-PU-2026-7359
ALT-PU-2026-7359: package `kernel-image-std-def` update to version 5.10.253-alt1
ALT-PU-2026-7109
ALT-PU-2026-7109: package `kernel-image-rt` update to version 5.10.254-alt1.rt150
ALT-PU-2026-6793
ALT-PU-2026-6793: package `kernel-image-6.18` update to version 6.18.22-alt1
ALT-PU-2026-7584
ALT-PU-2026-7584: package `kernel-image-rpi-un` update to version 6.12.86-alt1
ELSA-2026-50372
ELSA-2026-50372: Unbreakable Enterprise kernel security update (IMPORTANT)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-43050 In the Linux kernel, the following vulnerability has been resolved: atm: lec: fix use-after-free in sock_def_readable() A race condition exists between lec_atm_close() setting priv->lecd to NULL and concurrent access to priv->lecd in send_to_lecd(), lec_handle_bridge(), and lec_atm_send(). When the socket is freed via RCU while another thread is still using it, a use-after-free occurs in sock_def_readable() when accessing the socket's wait queue. The root cause is that lec_atm_close() clears priv->lecd without any synchronization, while callers dereference priv->lecd without any protection against concurrent teardown. Fix this by converting priv->lecd to an RCU-protected pointer: - Mark priv->lecd as __rcu in lec.h - Use rcu_assign_pointer() in lec_atm_close() and lecd_attach() for safe pointer assignment - Use rcu_access_pointer() for NULL checks that do not dereference the pointer in lec_start_xmit(), lec_push(), send_to_lecd() and lecd_attach() - Use rcu_read_lock/rcu_dereference... | CVSS3: 7 | 0% Низкий | 6 месяцев назад | |
CVE-2026-43050 In the Linux kernel, the following vulnerability has been resolved: atm: lec: fix use-after-free in sock_def_readable() A race condition exists between lec_atm_close() setting priv->lecd to NULL and concurrent access to priv->lecd in send_to_lecd(), lec_handle_bridge(), and lec_atm_send(). When the socket is freed via RCU while another thread is still using it, a use-after-free occurs in sock_def_readable() when accessing the socket's wait queue. The root cause is that lec_atm_close() clears priv->lecd without any synchronization, while callers dereference priv->lecd without any protection against concurrent teardown. Fix this by converting priv->lecd to an RCU-protected pointer: - Mark priv->lecd as __rcu in lec.h - Use rcu_assign_pointer() in lec_atm_close() and lecd_attach() for safe pointer assignment - Use rcu_access_pointer() for NULL checks that do not dereference the pointer in lec_start_xmit(), lec_push(), send_to_lecd() and lecd_attach() - Use rcu_read_lock/rcu_dereference... | CVSS3: 5.5 | 0% Низкий | 6 месяцев назад | |
CVE-2026-43050 In the Linux kernel, the following vulnerability has been resolved: atm: lec: fix use-after-free in sock_def_readable() A race condition exists between lec_atm_close() setting priv->lecd to NULL and concurrent access to priv->lecd in send_to_lecd(), lec_handle_bridge(), and lec_atm_send(). When the socket is freed via RCU while another thread is still using it, a use-after-free occurs in sock_def_readable() when accessing the socket's wait queue. The root cause is that lec_atm_close() clears priv->lecd without any synchronization, while callers dereference priv->lecd without any protection against concurrent teardown. Fix this by converting priv->lecd to an RCU-protected pointer: - Mark priv->lecd as __rcu in lec.h - Use rcu_assign_pointer() in lec_atm_close() and lecd_attach() for safe pointer assignment - Use rcu_access_pointer() for NULL checks that do not dereference the pointer in lec_start_xmit(), lec_push(), send_to_lecd() and lecd_attach() - Use rcu_read_lock/rcu_dere | CVSS3: 7 | 0% Низкий | 6 месяцев назад | |
CVE-2026-43050 In the Linux kernel, the following vulnerability has been resolved: a ... | CVSS3: 7 | 0% Низкий | 6 месяцев назад | |
GHSA-jhj6-5p6x-hw75 In the Linux kernel, the following vulnerability has been resolved: atm: lec: fix use-after-free in sock_def_readable() A race condition exists between lec_atm_close() setting priv->lecd to NULL and concurrent access to priv->lecd in send_to_lecd(), lec_handle_bridge(), and lec_atm_send(). When the socket is freed via RCU while another thread is still using it, a use-after-free occurs in sock_def_readable() when accessing the socket's wait queue. The root cause is that lec_atm_close() clears priv->lecd without any synchronization, while callers dereference priv->lecd without any protection against concurrent teardown. Fix this by converting priv->lecd to an RCU-protected pointer: - Mark priv->lecd as __rcu in lec.h - Use rcu_assign_pointer() in lec_atm_close() and lecd_attach() for safe pointer assignment - Use rcu_access_pointer() for NULL checks that do not dereference the pointer in lec_start_xmit(), lec_push(), send_to_lecd() and lecd_attach() - Use rcu_read_lock/rcu_d... | CVSS3: 7 | 0% Низкий | 6 месяцев назад | |
BDU:2026-07835 Уязвимость функции sock_def_readable() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 8 | 0% Низкий | 8 месяцев назад | |
ROS-20260918-80-0029 Уязвимость kernel-lt | CVSS3: 8 | 0% Низкий | около 1 месяца назад | |
ROS-20260918-73-0027 Уязвимость kernel-lt | CVSS3: 8 | 0% Низкий | около 1 месяца назад | |
SUSE-SU-2026:2202-1 Security update for the Linux Kernel | 5 месяцев назад | |||
SUSE-SU-2026:2215-1 Security update for the Linux Kernel | 5 месяцев назад | |||
SUSE-SU-2026:2195-1 Security update for the Linux Kernel | 4 месяца назад | |||
SUSE-SU-2026:2217-1 Security update for the Linux Kernel | 5 месяцев назад | |||
SUSE-SU-2026:2238-1 Security update for the Linux Kernel | 4 месяца назад | |||
openSUSE-SU-2026:20826-1 Security update for the Linux Kernel | 5 месяцев назад | |||
ALT-PU-2026-6805 ALT-PU-2026-6805: package `kernel-image-un-def` update to version 6.1.168-alt1 | CVSS3: 9.8 | 6 месяцев назад | ||
ALT-PU-2026-7359 ALT-PU-2026-7359: package `kernel-image-std-def` update to version 5.10.253-alt1 | CVSS3: 9.8 | 6 месяцев назад | ||
ALT-PU-2026-7109 ALT-PU-2026-7109: package `kernel-image-rt` update to version 5.10.254-alt1.rt150 | CVSS3: 9.8 | 6 месяцев назад | ||
ALT-PU-2026-6793 ALT-PU-2026-6793: package `kernel-image-6.18` update to version 6.18.22-alt1 | CVSS3: 9.8 | 6 месяцев назад | ||
ALT-PU-2026-7584 ALT-PU-2026-7584: package `kernel-image-rpi-un` update to version 6.12.86-alt1 | CVSS3: 9.8 | 5 месяцев назад | ||
ELSA-2026-50372 ELSA-2026-50372: Unbreakable Enterprise kernel security update (IMPORTANT) | 4 месяца назад |
Уязвимостей на страницу