ipv6: fix possible infinite loop in fib6_select_path()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d9ccb18f83ea2bb654289b6ecf014fd267cc988b · < 9c7da87c2dc860bb17ca1ece942495d28b1ce3b9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipv6: fix possible infinite loop in fib6_select_path()
Found while auditing the same pattern Sashiko reported in rt6_fill_node() [1]. Apply the same fix as commit f8d8ce1b515a ("ipv6: fix possible infinite loop in fib6_info_uses_dev()").
Writers holding tb6_lock can list_del_rcu(&first->fib6_siblings) without waiting for RCU readers; first->fib6_siblings.next then still points into the old ring and this softirq-side walker never reaches &first->fib6_siblings as its terminator. fib6_purge_rt() always WRITE_ONCE()s first->fib6_nsiblings to 0 before list_del_rcu(), so an inside-loop check is a reliable detach signal.
[1] https://sashiko.dev/#/patchset/20260526020227.4857-1-jiayuan.chen%40linux.dev
From the CVE record · Linux
A race in the Linux kernel’s IPv6 fib6_select_path() can cause an infinite loop when a route sibling is removed while a softirq-side reader traverses the list. The input does not establish how an attacker could trigger the race or whether authentication or user interaction is required.
Engineers running Linux kernels should check their vendor’s advisory for affected versions; none are specified in the input.