Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-63969ipv6: fix possible infinite loop in rt6_fill_node()

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 months later

    First scored

    Medium 5.5

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63969, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (22 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d0ec61c9f3583b76aebdbb271f5c0d3fcccd48b2 – < b014a63d2f2c2c767762b548381882dfb1655529
    • affected 52da02521ede55fb86546c3fffd9377b3261b91f – < 279853aec9f58d5cd723e6e5617c1c3337b30383
    • affected 34a949e7a0869dfa31a40416d2a56973fae1807b – < c65b1f60237daac7c56c2652e064cc566a45dc81
    • affected d9ccb18f83ea2bb654289b6ecf014fd267cc988b – < dc36a04621dcc2447dae428709207810b6c06e14
    • affected d9ccb18f83ea2bb654289b6ecf014fd267cc988b – < 5e40de719ee76b8d96e2556ce36dbd3bd07bf37d
    • affected d9ccb18f83ea2bb654289b6ecf014fd267cc988b – < 9f72412bcf60144f252b0d6205106abf14344abc
    • affected 11edcd026012ac18acee0f1514db3ed1b160fc6f
    • affected 6.1.128 – < 6.1.176
    • affected 6.6.75 – < 6.6.143
    • affected 6.12.2 – < 6.12.93
    • affected 6.11.11 – < 6.12
  • Linux · Linux

    • affected 6.13
    • unaffected < 6.13
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63969 badge
[![CVE-2026-63969](https://cveledger.app/badge/CVE-2026-63969.svg)](https://cveledger.app/cve/CVE-2026-63969)

Record last updated .