Поиск уязвимостей
Количество 18
Количество 18
CVE-2024-26864
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix refcnt handling in __inet_hash_connect(). syzbot reported a warning in sk_nulls_del_node_init_rcu(). The commit 66b60b0c8c4a ("dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().") tried to fix an issue that an unconnected socket occupies an ehash entry when bhash2 allocation fails. In such a case, we need to revert changes done by check_established(), which does not hold refcnt when inserting socket into ehash. So, to revert the change, we need to __sk_nulls_add_node_rcu() instead of sk_nulls_add_node_rcu(). Otherwise, sock_put() will cause refcnt underflow and leak the socket. [0]: WARNING: CPU: 0 PID: 23948 at include/net/sock.h:799 sk_nulls_del_node_init_rcu+0x166/0x1a0 include/net/sock.h:799 Modules linked in: CPU: 0 PID: 23948 Comm: syz-executor.2 Not tainted 6.8.0-rc6-syzkaller-00159-gc055fc00c07b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS ...
CVE-2024-26864
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix refcnt handling in __inet_hash_connect(). syzbot reported a warning in sk_nulls_del_node_init_rcu(). The commit 66b60b0c8c4a ("dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().") tried to fix an issue that an unconnected socket occupies an ehash entry when bhash2 allocation fails. In such a case, we need to revert changes done by check_established(), which does not hold refcnt when inserting socket into ehash. So, to revert the change, we need to __sk_nulls_add_node_rcu() instead of sk_nulls_add_node_rcu(). Otherwise, sock_put() will cause refcnt underflow and leak the socket. [0]: WARNING: CPU: 0 PID: 23948 at include/net/sock.h:799 sk_nulls_del_node_init_rcu+0x166/0x1a0 include/net/sock.h:799 Modules linked in: CPU: 0 PID: 23948 Comm: syz-executor.2 Not tainted 6.8.0-rc6-syzkaller-00159-gc055fc00c07b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS ...
CVE-2024-26864
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix refcnt handling in __inet_hash_connect(). syzbot reported a warning in sk_nulls_del_node_init_rcu(). The commit 66b60b0c8c4a ("dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().") tried to fix an issue that an unconnected socket occupies an ehash entry when bhash2 allocation fails. In such a case, we need to revert changes done by check_established(), which does not hold refcnt when inserting socket into ehash. So, to revert the change, we need to __sk_nulls_add_node_rcu() instead of sk_nulls_add_node_rcu(). Otherwise, sock_put() will cause refcnt underflow and leak the socket. [0]: WARNING: CPU: 0 PID: 23948 at include/net/sock.h:799 sk_nulls_del_node_init_rcu+0x166/0x1a0 include/net/sock.h:799 Modules linked in: CPU: 0 PID: 23948 Comm: syz-executor.2 Not tainted 6.8.0-rc6-syzkaller-00159-gc055fc00c07b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, B
CVE-2024-26864
In the Linux kernel, the following vulnerability has been resolved: t ...
GHSA-vffh-vwhr-v5jp
In the Linux kernel, the following vulnerability has been resolved: tcp: Fix refcnt handling in __inet_hash_connect(). syzbot reported a warning in sk_nulls_del_node_init_rcu(). The commit 66b60b0c8c4a ("dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().") tried to fix an issue that an unconnected socket occupies an ehash entry when bhash2 allocation fails. In such a case, we need to revert changes done by check_established(), which does not hold refcnt when inserting socket into ehash. So, to revert the change, we need to __sk_nulls_add_node_rcu() instead of sk_nulls_add_node_rcu(). Otherwise, sock_put() will cause refcnt underflow and leak the socket. [0]: WARNING: CPU: 0 PID: 23948 at include/net/sock.h:799 sk_nulls_del_node_init_rcu+0x166/0x1a0 include/net/sock.h:799 Modules linked in: CPU: 0 PID: 23948 Comm: syz-executor.2 Not tainted 6.8.0-rc6-syzkaller-00159-gc055fc00c07b #0 Hardware name: Google Google Compute Engine/Google Compute Engine...
BDU:2025-04400
Уязвимость функции __inet_hash_connect() модуля net/ipv4/inet_hashtables.c реализации протокола IPv4 ядра операционной системы Linux, позволяющая нарушителю получить доступ к защищаемой информации
ROS-20241028-04
Множественные уязвимости kernel-lt
ALT-PU-2024-18365
ALT-PU-2024-18365: package `kernel-image-std-def` update to version 6.1.83-alt1
ALT-PU-2024-18257
ALT-PU-2024-18257: package `kernel-image-rt` update to version 6.1.83-alt1.rt28
ALT-PU-2024-18058
ALT-PU-2024-18058: package `kernel-image-un-def` update to version 6.1.83-alt1
ALT-PU-2024-18469
ALT-PU-2024-18469: package `kernel-image-un-def` update to version 6.6.23-alt1
ALT-PU-2024-18211
ALT-PU-2024-18211: package `kernel-image-pine` update to version 6.6.23-alt1
SUSE-SU-2024:4316-1
Security update for the Linux Kernel
SUSE-SU-2024:4314-1
Security update for the Linux Kernel
ALT-PU-2024-18141
ALT-PU-2024-18141: package `kernel-image-6.8` update to version 6.8.2-alt1
SUSE-SU-2024:4387-1
Security update for the Linux Kernel
SUSE-SU-2024:4318-1
Security update for the Linux Kernel
ALT-PU-2024-18117
ALT-PU-2024-18117: package `kernel-image-mp` update to version 6.7.12-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-26864 In the Linux kernel, the following vulnerability has been resolved: tcp: Fix refcnt handling in __inet_hash_connect(). syzbot reported a warning in sk_nulls_del_node_init_rcu(). The commit 66b60b0c8c4a ("dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().") tried to fix an issue that an unconnected socket occupies an ehash entry when bhash2 allocation fails. In such a case, we need to revert changes done by check_established(), which does not hold refcnt when inserting socket into ehash. So, to revert the change, we need to __sk_nulls_add_node_rcu() instead of sk_nulls_add_node_rcu(). Otherwise, sock_put() will cause refcnt underflow and leak the socket. [0]: WARNING: CPU: 0 PID: 23948 at include/net/sock.h:799 sk_nulls_del_node_init_rcu+0x166/0x1a0 include/net/sock.h:799 Modules linked in: CPU: 0 PID: 23948 Comm: syz-executor.2 Not tainted 6.8.0-rc6-syzkaller-00159-gc055fc00c07b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS ... | CVSS3: 7.8 | 1% Низкий | больше 2 лет назад | |
CVE-2024-26864 In the Linux kernel, the following vulnerability has been resolved: tcp: Fix refcnt handling in __inet_hash_connect(). syzbot reported a warning in sk_nulls_del_node_init_rcu(). The commit 66b60b0c8c4a ("dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().") tried to fix an issue that an unconnected socket occupies an ehash entry when bhash2 allocation fails. In such a case, we need to revert changes done by check_established(), which does not hold refcnt when inserting socket into ehash. So, to revert the change, we need to __sk_nulls_add_node_rcu() instead of sk_nulls_add_node_rcu(). Otherwise, sock_put() will cause refcnt underflow and leak the socket. [0]: WARNING: CPU: 0 PID: 23948 at include/net/sock.h:799 sk_nulls_del_node_init_rcu+0x166/0x1a0 include/net/sock.h:799 Modules linked in: CPU: 0 PID: 23948 Comm: syz-executor.2 Not tainted 6.8.0-rc6-syzkaller-00159-gc055fc00c07b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS ... | CVSS3: 5.5 | 1% Низкий | больше 2 лет назад | |
CVE-2024-26864 In the Linux kernel, the following vulnerability has been resolved: tcp: Fix refcnt handling in __inet_hash_connect(). syzbot reported a warning in sk_nulls_del_node_init_rcu(). The commit 66b60b0c8c4a ("dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().") tried to fix an issue that an unconnected socket occupies an ehash entry when bhash2 allocation fails. In such a case, we need to revert changes done by check_established(), which does not hold refcnt when inserting socket into ehash. So, to revert the change, we need to __sk_nulls_add_node_rcu() instead of sk_nulls_add_node_rcu(). Otherwise, sock_put() will cause refcnt underflow and leak the socket. [0]: WARNING: CPU: 0 PID: 23948 at include/net/sock.h:799 sk_nulls_del_node_init_rcu+0x166/0x1a0 include/net/sock.h:799 Modules linked in: CPU: 0 PID: 23948 Comm: syz-executor.2 Not tainted 6.8.0-rc6-syzkaller-00159-gc055fc00c07b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, B | CVSS3: 7.8 | 1% Низкий | больше 2 лет назад | |
CVE-2024-26864 In the Linux kernel, the following vulnerability has been resolved: t ... | CVSS3: 7.8 | 1% Низкий | больше 2 лет назад | |
GHSA-vffh-vwhr-v5jp In the Linux kernel, the following vulnerability has been resolved: tcp: Fix refcnt handling in __inet_hash_connect(). syzbot reported a warning in sk_nulls_del_node_init_rcu(). The commit 66b60b0c8c4a ("dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().") tried to fix an issue that an unconnected socket occupies an ehash entry when bhash2 allocation fails. In such a case, we need to revert changes done by check_established(), which does not hold refcnt when inserting socket into ehash. So, to revert the change, we need to __sk_nulls_add_node_rcu() instead of sk_nulls_add_node_rcu(). Otherwise, sock_put() will cause refcnt underflow and leak the socket. [0]: WARNING: CPU: 0 PID: 23948 at include/net/sock.h:799 sk_nulls_del_node_init_rcu+0x166/0x1a0 include/net/sock.h:799 Modules linked in: CPU: 0 PID: 23948 Comm: syz-executor.2 Not tainted 6.8.0-rc6-syzkaller-00159-gc055fc00c07b #0 Hardware name: Google Google Compute Engine/Google Compute Engine... | CVSS3: 5.9 | 1% Низкий | больше 2 лет назад | |
BDU:2025-04400 Уязвимость функции __inet_hash_connect() модуля net/ipv4/inet_hashtables.c реализации протокола IPv4 ядра операционной системы Linux, позволяющая нарушителю получить доступ к защищаемой информации | CVSS3: 5.9 | 1% Низкий | больше 2 лет назад | |
ROS-20241028-04 Множественные уязвимости kernel-lt | CVSS3: 5.5 | около 2 лет назад | ||
ALT-PU-2024-18365 ALT-PU-2024-18365: package `kernel-image-std-def` update to version 6.1.83-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-18257 ALT-PU-2024-18257: package `kernel-image-rt` update to version 6.1.83-alt1.rt28 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-18058 ALT-PU-2024-18058: package `kernel-image-un-def` update to version 6.1.83-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-18469 ALT-PU-2024-18469: package `kernel-image-un-def` update to version 6.6.23-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-18211 ALT-PU-2024-18211: package `kernel-image-pine` update to version 6.6.23-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
SUSE-SU-2024:4316-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:4314-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2024-18141 ALT-PU-2024-18141: package `kernel-image-6.8` update to version 6.8.2-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
SUSE-SU-2024:4387-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:4318-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2024-18117 ALT-PU-2024-18117: package `kernel-image-mp` update to version 6.7.12-alt1 | CVSS3: 9.1 | больше 2 лет назад |
Уязвимостей на страницу