CVE-2025-71097

published 13 Jan 2026 · updated 12 Nov 2026

ipv4: Fix reference count leak when using error routes with nexthop objects

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel ee4183501ea556dca31f5ffd8690aa9fd25b609f, Kernel 6.1.160, Kernel 5.10.248 and 10 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=493ced1ac47c48bb86d9d4e8e87df8592be85a0e <ee4183501ea556dca31f5ffd8690aa9fd25b609f, >=5.16 <6.1.160, >=5.3.1 <5.10.248, >=6.13 <6.18.4, >=6.2 <6.6.120, >=6.7 <6.12.64, =5.3, =6.19, >=493ced1ac47c48bb86d9d4e8e87df8592be85a0e <33ff5c207c873215e54e6176624ed57423cb7dea, >=493ced1ac47c48bb86d9d4e8e87df8592be85a0e <5979338c83012110ccd45cae6517591770bfe536, >=493ced1ac47c48bb86d9d4e8e87df8592be85a0e <5de7ad7e18356e39e8fbf7edd185a5faaf4f385a, >=493ced1ac47c48bb86d9d4e8e87df8592be85a0e <ac782f4e3bfcde145b8a7f8af31d9422d94d172a, >=493ced1ac47c48bb86d9d4e8e87df8592be85a0e <e3fc381320d04e4a74311e576a86cac49a16fc43, >=5.11 <5.15.198, >=493ced1ac47c48bb86d9d4e8e87df8592be85a0e <30386e090c49e803c0616a7147e43409c32a2b0eee4183501ea556dca31f5ffd8690aa9fd25b609f, 6.1.160, 5.10.248, 6.18.4, 6.6.120, 6.12.64, 33ff5c207c873215e54e6176624ed57423cb7dea, 5979338c83012110ccd45cae6517591770bfe536, 5de7ad7e18356e39e8fbf7edd185a5faaf4f385a, ac782f4e3bfcde145b8a7f8af31d9422d94d172a, e3fc381320d04e4a74311e576a86cac49a16fc43, 5.15.198, 30386e090c49e803c0616a7147e43409c32a2b0e
linux-kernel: Kernel>=5.11.0 <5.15.198, >=5.16.0 <6.1.160, >=5.3.0 <5.10.248, >=6.13.0 <6.18.4, >=6.2.0 <6.6.120, >=6.7.0 <6.12.645.15.198, 6.1.160, 5.10.248, 6.18.4, 6.6.120, 6.12.64

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-71097 severity on Zeptric[![CVE-2025-71097](https://zeptric.io/badge/cve/CVE-2025-71097.svg)](https://zeptric.io/cve/CVE-2025-71097)