Skip to main content

Linux Kernel CVE-2026-63968

| EUVDEUVD-2026-45741 HIGH
2026-07-19 Linux GHSA-c2hg-pgqh-6wp2
7.5
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.9 MEDIUM

Network-reachable DoS with no auth (PR:N) and availability-only impact, but winning the RCU list-deletion race is timing-dependent, so AC:H rather than AC:L.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 16:34 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
7.5 (HIGH)
Patch available
Jul 19, 2026 - 17:19 EUVD
CVE Published
Jul 19, 2026 - 14:55 cve.org
HIGH 7.5
CVE Published
Jul 19, 2026 - 14:55 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

AnalysisAI

Denial of service in the Linux kernel's IPv6 routing stack allows remote attackers to trigger an infinite loop in fib6_select_path(), hanging a CPU in softirq context and causing a system-wide hang or hard lockup. The flaw exists because writers holding tb6_lock can list_del_rcu() a route's fib6_siblings entry without waiting for RCU readers, leaving the softirq-side path-selection walker traversing a stale sibling ring that never reaches its list terminator. A vendor patch is available; EPSS is low (0.21%) and there is no public exploit identified at time of analysis, but the network-triggerable, no-privilege CVSS 7.5 vector makes it a meaningful availability risk on multipath IPv6 deployments.

Technical ContextAI

The vulnerable code is in the IPv6 FIB (Forwarding Information Base) multipath routing logic (net/ipv6/route.c). fib6_select_path() walks the fib6_siblings list - an RCU-protected circular linked list of equal-cost multipath (ECMP) route siblings - during packet forwarding/route lookup in softirq context. The kernel uses RCU for lock-free read-side traversal while writers hold tb6_lock. When a writer calls list_del_rcu(&first->fib6_siblings) to detach a route, the removed node's .next pointer still references the old ring, so a concurrent reader that captured the pre-deletion state can loop forever because it never encounters the &first->fib6_siblings terminator. The fix mirrors commit f8d8ce1b515a (the analogous fib6_info_uses_dev() fix) and the rt6_fill_node() pattern: fib6_purge_rt() always WRITE_ONCE()s first->fib6_nsiblings to 0 before the list_del_rcu(), so the walker adds an inside-loop check on fib6_nsiblings as a reliable detach signal to break out. This is a classic RCU list-deletion/reader-writer race (root cause class akin to CWE-835 Loop with Unreachable Exit Condition / CWE-362 concurrency race), though NVD lists CWE as N/A. Per CPE the affected component is the linux:linux kernel across the stable series.

RemediationAI

Vendor-released patch: update to a fixed stable kernel - 6.6.143 or later for the 6.6 branch, 6.1.176 or later for the 6.1 branch, 6.12.93 or later for the 6.12 branch, or the corresponding 6.18.35+/mainline build; apply your distribution's kernel update that incorporates the referenced stable commits (see https://git.kernel.org/stable/c/3948a7d92f7678e89e1776bb2d169afcad63b1ae and the sibling commits, and https://nvd.nist.gov/vuln/detail/CVE-2026-63968). If immediate patching or reboot is not possible, the practical compensating control is to reduce exposure of the vulnerable IPv6 multipath path: avoid/remove ECMP (equal-cost multipath) IPv6 routes with sibling entries where feasible, since the bug is only reachable when fib6_siblings rings are being traversed and mutated - trade-off is loss of IPv6 load-balancing/redundancy. On hosts that do not need IPv6 forwarding, disable IPv6 routing/forwarding (net.ipv6.conf.all.forwarding=0) or disable IPv6 entirely, accepting the loss of IPv6 connectivity. There is no reliable feature-flag workaround that preserves multipath routing, so scheduling the kernel update remains the correct fix.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-63968 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy