همهٔ گزارش‌ها
متوسط

kernel: Linux kernel (IPv4): Denial of Service due to reference count leak in nexthop objects

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده

بهره‌برداری

CVE-2025-71097

احتمال بهره‌برداری در ۳۰ روز آینده: 0.14%

FIRST EPSS · ۱۴۰۵/۰۸/۲۸

شرح آسیب‌پذیری

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: waiting for dummy1 to become free. Usage count = 2 Fix by flushing error routes when their nexthop is marked as dead. IPv6 does not suffer from this problem.

A flaw was found in the Linux kernel's IPv4 networking subsystem. A local attacker with low privileges could exploit a reference count leak when nexthop objects are deleted. This occurs because error routes, such as blackhole routes, are not properly flushed, causing them to retain a reference to the deleted nexthop object and its associated device. This vulnerability can lead to a Denial of Service (DoS) due to resource exhaustion, preventing the affected nexthop device from being freed.