CVE-2026-63969
CVE CVE-2026-63969EUVD EUVD-2026-45742Published 2026-07-19T14:55:56.000Z
What the advisory describes
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
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.12.93; 6.6.75 <6.6.143; d0ec61c9f3583b76aebdbb271f5c0d3fcccd48b2 <b014a63d2f2c2c767762b548381882dfb1655529; 6.13; 6.11.11 <6.12; patch: 6.6.143; 52da02521ede55fb86546c3fffd9377b3261b91f <279853aec9f58d5cd723e6e5617c1c3337b30383; 11edcd026012ac18acee0f1514db3ed1b160fc6f; d9ccb18f83ea2bb654289b6ecf014fd267cc988b <5e40de719ee76b8d96e2556ce36dbd3bd07bf37d; patch: 6.1.176; patch: 6.18.35; d9ccb18f83ea2bb654289b6ecf014fd267cc988b <9f72412bcf60144f252b0d6205106abf14344abc; patch: 7.1; 6.1.128 <6.1.176; 34a949e7a0869dfa31a40416d2a56973fae1807b <c65b1f60237daac7c56c2652e064cc566a45dc81; 6.12.2 <6.12.93; patch: 7.0.12; patch: 0; d9ccb18f83ea2bb654289b6ecf014fd267cc988b <dc36a04621dcc2447dae428709207810b6c06e14
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.