CVE-2026-63969

ipv6: fix possible infinite loop in rt6_fill_node()

N/A
Published: July 19, 2026 at 02:55 PM UTC
Updated: July 30, 2026 at 06:22 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: fix possible infinite loop in rt6_fill_node() Sashiko reported this issue [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(&rt->fib6_siblings) without waiting for RCU readers; rt->fib6_siblings.next then still points into the old ring and this softirq-side walker never reaches &rt->fib6_siblings, causing a CPU stall. fib6_del_route() always WRITE_ONCE()s rt->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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.11.116.1.128 ≤ v < 6.1.1766.11.11 ≤ v < 6.126.12.2 ≤ v < 6.12.936.13 ≤ v < 6.18.356.13 ≤ v < 7.0.126.13 ≤ v < 7.16.6.75 ≤ v < 6.6.14311edcd026012ac18acee0f1514db3ed1b160fc6f34a949e7a0869dfa31a40416d2a56973fae1807b52da02521ede55fb86546c3fffd9377b3261b91f6.1.1286.11.116.12.26.136.6.75d0ec61c9f3583b76aebdbb271f5c0d3fcccd48b2d9ccb18f83ea2bb654289b6ecf014fd267cc988b
Vendor states this is fixed in 279853aec9f58d5cd723e6e5617c1c3337b30383 (fixed)
Vendor states this is fixed in 5e40de719ee76b8d96e2556ce36dbd3bd07bf37d (fixed)
Vendor states this is fixed in 9f72412bcf60144f252b0d6205106abf14344abc (fixed)
Vendor states this is fixed in b014a63d2f2c2c767762b548381882dfb1655529 (fixed)
Vendor states this is fixed in c65b1f60237daac7c56c2652e064cc566a45dc81 (fixed)
Vendor states this is fixed in dc36a04621dcc2447dae428709207810b6c06e14 (fixed)
Vendor states this is fixed in 6.1.176 (unaffected)
Affected range stops below 6.12, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.93 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.18.35 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.12 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusAWAITING ANALYSIS

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card