Поиск уязвимостей
Количество 23
Количество 23
CVE-2025-71097
In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix reference count leak when using error routes with nexthop objects When a nexthop object is deleted, it is marked as dead and then fib_table_flush() is called to flush all the routes that are using the dead nexthop. The current logic in fib_table_flush() is to only flush error routes (e.g., blackhole) when it is called as part of network namespace dismantle (i.e., with flush_all=true). Therefore, error routes are not flushed when their nexthop object is deleted: # ip link add name dummy1 up type dummy # ip nexthop add id 1 dev dummy1 # ip route add 198.51.100.1/32 nhid 1 # ip route add blackhole 198.51.100.2/32 nhid 1 # ip nexthop del id 1 # ip route show blackhole 198.51.100.2 nhid 1 dev dummy1 As such, they keep holding a reference on the nexthop object which in turn holds a reference on the nexthop device, resulting in a reference count leak: # ip link del dev dummy1 [ 70.516258] unregister_netdevice: ...
CVE-2025-71097
In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix reference count leak when using error routes with nexthop objects When a nexthop object is deleted, it is marked as dead and then fib_table_flush() is called to flush all the routes that are using the dead nexthop. The current logic in fib_table_flush() is to only flush error routes (e.g., blackhole) when it is called as part of network namespace dismantle (i.e., with flush_all=true). Therefore, error routes are not flushed when their nexthop object is deleted: # ip link add name dummy1 up type dummy # ip nexthop add id 1 dev dummy1 # ip route add 198.51.100.1/32 nhid 1 # ip route add blackhole 198.51.100.2/32 nhid 1 # ip nexthop del id 1 # ip route show blackhole 198.51.100.2 nhid 1 dev dummy1 As such, they keep holding a reference on the nexthop object which in turn holds a reference on the nexthop device, resulting in a reference count leak: # ip link del dev dummy1 [ 70.516258] unregister_netdevice: ...
CVE-2025-71097
In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix reference count leak when using error routes with nexthop objects When a nexthop object is deleted, it is marked as dead and then fib_table_flush() is called to flush all the routes that are using the dead nexthop. The current logic in fib_table_flush() is to only flush error routes (e.g., blackhole) when it is called as part of network namespace dismantle (i.e., with flush_all=true). Therefore, error routes are not flushed when their nexthop object is deleted: # ip link add name dummy1 up type dummy # ip nexthop add id 1 dev dummy1 # ip route add 198.51.100.1/32 nhid 1 # ip route add blackhole 198.51.100.2/32 nhid 1 # ip nexthop del id 1 # ip route show blackhole 198.51.100.2 nhid 1 dev dummy1 As such, they keep holding a reference on the nexthop object which in turn holds a reference on the nexthop device, resulting in a reference count leak: # ip link del dev dummy1 [ 70.516258] unregister
CVE-2025-71097
ipv4: Fix reference count leak when using error routes with nexthop objects
CVE-2025-71097
In the Linux kernel, the following vulnerability has been resolved: i ...
GHSA-hc39-xg82-jgf4
In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix reference count leak when using error routes with nexthop objects When a nexthop object is deleted, it is marked as dead and then fib_table_flush() is called to flush all the routes that are using the dead nexthop. The current logic in fib_table_flush() is to only flush error routes (e.g., blackhole) when it is called as part of network namespace dismantle (i.e., with flush_all=true). Therefore, error routes are not flushed when their nexthop object is deleted: # ip link add name dummy1 up type dummy # ip nexthop add id 1 dev dummy1 # ip route add 198.51.100.1/32 nhid 1 # ip route add blackhole 198.51.100.2/32 nhid 1 # ip nexthop del id 1 # ip route show blackhole 198.51.100.2 nhid 1 dev dummy1 As such, they keep holding a reference on the nexthop object which in turn holds a reference on the nexthop device, resulting in a reference count leak: # ip link del dev dummy1 [ 70.516258] unregis...
BDU:2026-08858
Уязвимость функции fib_table_flush() модуля net/ipv4/fib_trie.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260929-80-0205
Уязвимость kernel-lt
ROS-20260929-73-0177
Уязвимость kernel-lt
ALT-PU-2026-3159
ALT-PU-2026-3159: package `kernel-image-rt` update to version 5.10.248-alt1.rt143
ALT-PU-2026-2816
ALT-PU-2026-2816: package `kernel-image-std-def` update to version 5.10.248-alt1
ALT-PU-2026-3819
ALT-PU-2026-3819: package `kernel-image-un-def` update to version 6.1.160-alt1
ALT-PU-2026-3823
ALT-PU-2026-3823: package `kernel-image-rt` update to version 6.12.65-alt1
ALT-PU-2026-3822
ALT-PU-2026-3822: package `kernel-image-6.12` update to version 6.12.65-alt1
ELSA-2026-50145
ELSA-2026-50145: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2026:0587-1
Security update for the Linux Kernel
SUSE-SU-2026:0447-1
Security update for the Linux Kernel
SUSE-SU-2026:0472-1
Security update for the Linux Kernel
ELSA-2026-50112
ELSA-2026-50112: Unbreakable Enterprise kernel security update (IMPORTANT)
openSUSE-SU-2026:20287-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-71097 In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix reference count leak when using error routes with nexthop objects When a nexthop object is deleted, it is marked as dead and then fib_table_flush() is called to flush all the routes that are using the dead nexthop. The current logic in fib_table_flush() is to only flush error routes (e.g., blackhole) when it is called as part of network namespace dismantle (i.e., with flush_all=true). Therefore, error routes are not flushed when their nexthop object is deleted: # ip link add name dummy1 up type dummy # ip nexthop add id 1 dev dummy1 # ip route add 198.51.100.1/32 nhid 1 # ip route add blackhole 198.51.100.2/32 nhid 1 # ip nexthop del id 1 # ip route show blackhole 198.51.100.2 nhid 1 dev dummy1 As such, they keep holding a reference on the nexthop object which in turn holds a reference on the nexthop device, resulting in a reference count leak: # ip link del dev dummy1 [ 70.516258] unregister_netdevice: ... | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
CVE-2025-71097 In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix reference count leak when using error routes with nexthop objects When a nexthop object is deleted, it is marked as dead and then fib_table_flush() is called to flush all the routes that are using the dead nexthop. The current logic in fib_table_flush() is to only flush error routes (e.g., blackhole) when it is called as part of network namespace dismantle (i.e., with flush_all=true). Therefore, error routes are not flushed when their nexthop object is deleted: # ip link add name dummy1 up type dummy # ip nexthop add id 1 dev dummy1 # ip route add 198.51.100.1/32 nhid 1 # ip route add blackhole 198.51.100.2/32 nhid 1 # ip nexthop del id 1 # ip route show blackhole 198.51.100.2 nhid 1 dev dummy1 As such, they keep holding a reference on the nexthop object which in turn holds a reference on the nexthop device, resulting in a reference count leak: # ip link del dev dummy1 [ 70.516258] unregister_netdevice: ... | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
CVE-2025-71097 In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix reference count leak when using error routes with nexthop objects When a nexthop object is deleted, it is marked as dead and then fib_table_flush() is called to flush all the routes that are using the dead nexthop. The current logic in fib_table_flush() is to only flush error routes (e.g., blackhole) when it is called as part of network namespace dismantle (i.e., with flush_all=true). Therefore, error routes are not flushed when their nexthop object is deleted: # ip link add name dummy1 up type dummy # ip nexthop add id 1 dev dummy1 # ip route add 198.51.100.1/32 nhid 1 # ip route add blackhole 198.51.100.2/32 nhid 1 # ip nexthop del id 1 # ip route show blackhole 198.51.100.2 nhid 1 dev dummy1 As such, they keep holding a reference on the nexthop object which in turn holds a reference on the nexthop device, resulting in a reference count leak: # ip link del dev dummy1 [ 70.516258] unregister | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
CVE-2025-71097 ipv4: Fix reference count leak when using error routes with nexthop objects | CVSS3: 6.5 | 0% Низкий | 10 месяцев назад | |
CVE-2025-71097 In the Linux kernel, the following vulnerability has been resolved: i ... | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
GHSA-hc39-xg82-jgf4 In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix reference count leak when using error routes with nexthop objects When a nexthop object is deleted, it is marked as dead and then fib_table_flush() is called to flush all the routes that are using the dead nexthop. The current logic in fib_table_flush() is to only flush error routes (e.g., blackhole) when it is called as part of network namespace dismantle (i.e., with flush_all=true). Therefore, error routes are not flushed when their nexthop object is deleted: # ip link add name dummy1 up type dummy # ip nexthop add id 1 dev dummy1 # ip route add 198.51.100.1/32 nhid 1 # ip route add blackhole 198.51.100.2/32 nhid 1 # ip nexthop del id 1 # ip route show blackhole 198.51.100.2 nhid 1 dev dummy1 As such, they keep holding a reference on the nexthop object which in turn holds a reference on the nexthop device, resulting in a reference count leak: # ip link del dev dummy1 [ 70.516258] unregis... | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
BDU:2026-08858 Уязвимость функции fib_table_flush() модуля net/ipv4/fib_trie.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 11 месяцев назад | |
ROS-20260929-80-0205 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
ROS-20260929-73-0177 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
ALT-PU-2026-3159 ALT-PU-2026-3159: package `kernel-image-rt` update to version 5.10.248-alt1.rt143 | CVSS3: 8.2 | 9 месяцев назад | ||
ALT-PU-2026-2816 ALT-PU-2026-2816: package `kernel-image-std-def` update to version 5.10.248-alt1 | CVSS3: 8.2 | 9 месяцев назад | ||
ALT-PU-2026-3819 ALT-PU-2026-3819: package `kernel-image-un-def` update to version 6.1.160-alt1 | CVSS3: 8.2 | 10 месяцев назад | ||
ALT-PU-2026-3823 ALT-PU-2026-3823: package `kernel-image-rt` update to version 6.12.65-alt1 | CVSS3: 8.2 | 10 месяцев назад | ||
ALT-PU-2026-3822 ALT-PU-2026-3822: package `kernel-image-6.12` update to version 6.12.65-alt1 | CVSS3: 8.2 | 10 месяцев назад | ||
ELSA-2026-50145 ELSA-2026-50145: Unbreakable Enterprise kernel security update (IMPORTANT) | 8 месяцев назад | |||
SUSE-SU-2026:0587-1 Security update for the Linux Kernel | 9 месяцев назад | |||
SUSE-SU-2026:0447-1 Security update for the Linux Kernel | 9 месяцев назад | |||
SUSE-SU-2026:0472-1 Security update for the Linux Kernel | 9 месяцев назад | |||
ELSA-2026-50112 ELSA-2026-50112: Unbreakable Enterprise kernel security update (IMPORTANT) | 9 месяцев назад | |||
openSUSE-SU-2026:20287-1 Security update for the Linux Kernel | 8 месяцев назад |
Уязвимостей на страницу