Поиск уязвимостей
Количество 55
Количество 55
BDU:2024-04585
Уязвимость функции __dst_negative_advice() реализации протокола IPv4 ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
CVE-2024-36971
In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets.
CVE-2024-36971
In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets.
CVE-2024-36971
In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets.
CVE-2024-36971
net: fix __dst_negative_advice() race
CVE-2024-36971
In the Linux kernel, the following vulnerability has been resolved: n ...
ROS-20240819-01
Множественные уязвимости kernel-lt
SUSE-SU-2025:0250-1
Security update for the Linux Kernel (Live Patch 22 for SLE 15 SP4)
SUSE-SU-2025:0242-1
Security update for the Linux Kernel (Live Patch 41 for SLE 15 SP3)
GHSA-3rf3-8wmx-cm8q
In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets.
SUSE-SU-2025:0241-1
Security update for the Linux Kernel (Live Patch 9 for SLE 15 SP5)
ELSA-2024-5259
ELSA-2024-5259: kernel security update (IMPORTANT)
SUSE-SU-2025:0246-1
Security update for the Linux Kernel (Live Patch 48 for SLE 15 SP3)
SUSE-SU-2025:0245-1
Security update for the Linux Kernel (Live Patch 47 for SLE 15 SP3)
ALT-PU-2024-9459
ALT-PU-2024-9459: package `kernel-image-rt` update to version 5.10.219-alt1.rt111
ALT-PU-2024-17597
ALT-PU-2024-17597: package `kernel-image-std-def` update to version 5.10.219-alt1
SUSE-SU-2025:0268-1
Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP6)
ALT-PU-2024-10855
ALT-PU-2024-10855: package `kernel-image-pine` update to version 6.10.3-alt2
SUSE-SU-2025:0263-1
Security update for the Linux Kernel (Live Patch 0 for SLE 15 SP6)
SUSE-SU-2025:0243-1
Security update for the Linux Kernel (Live Patch 46 for SLE 15 SP3)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2024-04585 Уязвимость функции __dst_negative_advice() реализации протокола IPv4 ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 7.8 | 3% Низкий | больше 2 лет назад | |
CVE-2024-36971 In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets. | CVSS3: 7.8 | 3% Низкий | больше 2 лет назад | |
CVE-2024-36971 In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets. | CVSS3: 7.8 | 3% Низкий | больше 2 лет назад | |
CVE-2024-36971 In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets. | CVSS3: 7.8 | 3% Низкий | больше 2 лет назад | |
CVE-2024-36971 net: fix __dst_negative_advice() race | CVSS3: 7.8 | 3% Низкий | около 2 лет назад | |
CVE-2024-36971 In the Linux kernel, the following vulnerability has been resolved: n ... | CVSS3: 7.8 | 3% Низкий | больше 2 лет назад | |
ROS-20240819-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | около 2 лет назад | ||
SUSE-SU-2025:0250-1 Security update for the Linux Kernel (Live Patch 22 for SLE 15 SP4) | 3% Низкий | почти 2 года назад | ||
SUSE-SU-2025:0242-1 Security update for the Linux Kernel (Live Patch 41 for SLE 15 SP3) | 3% Низкий | почти 2 года назад | ||
GHSA-3rf3-8wmx-cm8q In the Linux kernel, the following vulnerability has been resolved: net: fix __dst_negative_advice() race __dst_negative_advice() does not enforce proper RCU rules when sk->dst_cache must be cleared, leading to possible UAF. RCU rules are that we must first clear sk->sk_dst_cache, then call dst_release(old_dst). Note that sk_dst_reset(sk) is implementing this protocol correctly, while __dst_negative_advice() uses the wrong order. Given that ip6_negative_advice() has special logic against RTF_CACHE, this means each of the three ->negative_advice() existing methods must perform the sk_dst_reset() themselves. Note the check against NULL dst is centralized in __dst_negative_advice(), there is no need to duplicate it in various callbacks. Many thanks to Clement Lecigne for tracking this issue. This old bug became visible after the blamed commit, using UDP sockets. | CVSS3: 7.8 | 3% Низкий | больше 2 лет назад | |
SUSE-SU-2025:0241-1 Security update for the Linux Kernel (Live Patch 9 for SLE 15 SP5) | почти 2 года назад | |||
ELSA-2024-5259 ELSA-2024-5259: kernel security update (IMPORTANT) | около 2 лет назад | |||
SUSE-SU-2025:0246-1 Security update for the Linux Kernel (Live Patch 48 for SLE 15 SP3) | почти 2 года назад | |||
SUSE-SU-2025:0245-1 Security update for the Linux Kernel (Live Patch 47 for SLE 15 SP3) | почти 2 года назад | |||
ALT-PU-2024-9459 ALT-PU-2024-9459: package `kernel-image-rt` update to version 5.10.219-alt1.rt111 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-17597 ALT-PU-2024-17597: package `kernel-image-std-def` update to version 5.10.219-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
SUSE-SU-2025:0268-1 Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP6) | почти 2 года назад | |||
ALT-PU-2024-10855 ALT-PU-2024-10855: package `kernel-image-pine` update to version 6.10.3-alt2 | CVSS3: 8.1 | больше 2 лет назад | ||
SUSE-SU-2025:0263-1 Security update for the Linux Kernel (Live Patch 0 for SLE 15 SP6) | почти 2 года назад | |||
SUSE-SU-2025:0243-1 Security update for the Linux Kernel (Live Patch 46 for SLE 15 SP3) | почти 2 года назад |
Уязвимостей на страницу