CVE-2026-63917

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ip6: vti: Use ip6_tnl.net in vti6_changelink().

ip netns add ns1 ip netns add ns2 ip -n ns1 link add vti6_test type vti6 remote ::1 local ::2 key 7 ip -n ns1 link set vti6_test netns ns2 ip -n ns2 link set vti6_test type vti6 remote ::3 local ::4 key 9 ip netns del ns2 ip netns del ns1 [ 132.495484] ------------[ cut here ]------------ [ 132.497609] kernel BUG at net/core/dev.c:12376!

Commit 61220ab34948 ("vti6: Enable namespace changing") dropped NETIF_F_NETNS_LOCAL from vti6 devices. A vti6 tunnel can then move through IFLA_NET_NS_FD. After the move dev_net(dev) points at the new netns while t->net stays at the creation netns.

vti6_changelink() and vti6_update() still use dev_net(dev) and dev_net(t->dev). They unlink from one per netns hash and relink into another. The creation netns is left with a stale entry. cleanup_net() of that netns later walks freed memory.

Reachable from an unprivileged user namespace (unshare --user --map-root-user --net). Cross tenant scope on container hosts.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jul 20, 2026
No patch confirmed yet.
generic

ip6: vti: Use ip6_tnl.net in vti6_changelink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fc32be9ac2788524c6b24efd681cce7a6e731a92
generic

ip6: vti: Use ip6_tnl.net in vti6_changelink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f5c68875e25f331e497ddfbe81e2d8163a87f136
generic

ip6: vti: Use ip6_tnl.net in vti6_changelink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f1e89a943ee574d0f2f16246eb3f2d7330fdeb03
generic

ip6: vti: Use ip6_tnl.net in vti6_changelink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ee1778ba0f5cb53be771f97017d01eb356c797bf
generic

ip6: vti: Use ip6_tnl.net in vti6_changelink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d9c5eecdb3c740e65038651db7c686b10d76d1bc
generic

ip6: vti: Use ip6_tnl.net in vti6_changelink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/225b467e3b631f38be22e4b38062a1fed02fdd21
generic

ip6: vti: Use ip6_tnl.net in vti6_changelink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11b326fb0a374f4654f9be22d0f0f7abd9f7d3fe
generic

ip6: vti: Use ip6_tnl.net in vti6_changelink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cdce7618464f7fb06f461e8f4ad575cb1d570f4

Vendor Advisories for CVE-2026-63917(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 33× in last 7d / 164× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 212 total refreshes for this CVE.

  1. 2026-08-30 02:57 UTCEG score recompute
  2. 2026-08-30 02:57 UTCVendor advisory
  3. 2026-08-30 02:57 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 23:49 UTCEG score recompute
  7. 2026-08-27 23:49 UTCVendor advisory
  8. 2026-08-27 23:49 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 11:54 UTCVendor advisory
  11. 2026-08-27 11:54 UTCGHSA enrichment
  12. 2026-08-26 22:26 UTCEG score recompute
  13. 2026-08-26 22:26 UTCVendor advisory
  14. 2026-08-26 22:26 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 08:02 UTCVendor advisory
  17. 2026-08-26 08:02 UTCGHSA enrichment
  18. 2026-08-25 20:20 UTCEG score recompute
  19. 2026-08-25 20:20 UTCVendor advisory
  20. 2026-08-25 20:19 UTCGHSA enrichment
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 08:38 UTCVendor advisory
  23. 2026-08-25 08:38 UTCGHSA enrichment
  24. 2026-08-24 20:48 UTCEG score recompute
  25. 2026-08-24 20:48 UTCVendor advisory
Show 75 more
  1. 2026-08-24 20:48 UTCGHSA enrichment
  2. 2026-08-24 09:07 UTCVendor advisory
  3. 2026-08-24 09:07 UTCGHSA enrichment
  4. 2026-08-23 20:53 UTCVendor advisory
  5. 2026-08-23 20:53 UTCGHSA enrichment
  6. 2026-08-23 09:11 UTCEG score recompute
  7. 2026-08-23 09:11 UTCVendor advisory
  8. 2026-08-23 09:11 UTCGHSA enrichment
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 21:29 UTCVendor advisory
  11. 2026-08-22 21:29 UTCGHSA enrichment
  12. 2026-08-22 09:39 UTCEG score recompute
  13. 2026-08-22 09:39 UTCVendor advisory
  14. 2026-08-22 09:39 UTCGHSA enrichment
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 21:57 UTCVendor advisory
  17. 2026-08-21 21:57 UTCGHSA enrichment
  18. 2026-08-21 10:16 UTCEG score recompute
  19. 2026-08-21 10:16 UTCVendor advisory
  20. 2026-08-21 10:16 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 22:34 UTCVendor advisory
  23. 2026-08-20 22:34 UTCGHSA enrichment
  24. 2026-08-20 10:52 UTCVendor advisory
  25. 2026-08-20 10:52 UTCGHSA enrichment
  26. 2026-08-19 23:10 UTCEG score recompute
  27. 2026-08-19 23:10 UTCVendor advisory
  28. 2026-08-19 23:10 UTCGHSA enrichment
  29. 2026-08-19 17:04 UTCEPSS rescore
  30. 2026-08-19 09:43 UTCVendor advisory
  31. 2026-08-19 09:43 UTCGHSA enrichment
  32. 2026-08-18 21:49 UTCEG score recompute
  33. 2026-08-18 21:49 UTCVendor advisory
  34. 2026-08-18 21:49 UTCGHSA enrichment
  35. 2026-08-18 13:48 UTCEPSS rescore
  36. 2026-08-18 09:25 UTCVendor advisory
  37. 2026-08-18 09:25 UTCGHSA enrichment
  38. 2026-08-17 21:10 UTCEG score recompute
  39. 2026-08-17 21:10 UTCVendor advisory
  40. 2026-08-17 21:10 UTCGHSA enrichment
  41. 2026-08-17 13:47 UTCEPSS rescore
  42. 2026-08-17 06:06 UTCVendor advisory
  43. 2026-08-17 06:06 UTCGHSA enrichment
  44. 2026-08-16 18:25 UTCEG score recompute
  45. 2026-08-16 18:25 UTCVendor advisory
  46. 2026-08-16 18:25 UTCGHSA enrichment
  47. 2026-08-16 14:56 UTCEPSS rescore
  48. 2026-08-16 06:43 UTCEG score recompute
  49. 2026-08-16 06:43 UTCVendor advisory
  50. 2026-08-16 06:43 UTCGHSA enrichment
  51. 2026-08-15 19:02 UTCVendor advisory
  52. 2026-08-15 19:02 UTCGHSA enrichment
  53. 2026-08-15 07:20 UTCEG score recompute
  54. 2026-08-15 07:20 UTCVendor advisory
  55. 2026-08-15 07:20 UTCGHSA enrichment
  56. 2026-08-15 01:30 UTCEPSS rescore
  57. 2026-08-14 19:38 UTCVendor advisory
  58. 2026-08-14 19:38 UTCGHSA enrichment
  59. 2026-08-14 07:57 UTCEG score recompute
  60. 2026-08-14 07:57 UTCVendor advisory
  61. 2026-08-14 07:57 UTCGHSA enrichment
  62. 2026-08-13 22:00 UTCEPSS rescore
  63. 2026-08-13 20:15 UTCVendor advisory
  64. 2026-08-13 20:15 UTCGHSA enrichment
  65. 2026-08-13 08:34 UTCVendor advisory
  66. 2026-08-13 08:34 UTCGHSA enrichment
  67. 2026-08-12 20:51 UTCEG score recompute
  68. 2026-08-12 20:51 UTCVendor advisory
  69. 2026-08-12 20:51 UTCGHSA enrichment
  70. 2026-08-12 13:51 UTCEPSS rescore
  71. 2026-08-12 09:10 UTCVendor advisory
  72. 2026-08-12 09:10 UTCGHSA enrichment
  73. 2026-08-11 21:28 UTCEG score recompute
  74. 2026-08-11 21:28 UTCVendor advisory
  75. 2026-08-11 21:28 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-63917?
CVE-2026-63917 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ip6: vti: Use ip6tnl.net in vti6changelink(). ip netns add ns1 ip netns add ns2 ip -n ns1 link add vti6_test type vti6 remote ::1 local ::2 key 7 ip -n ns1 link set vti6_test netns ns2 ip -n ns2 link set vti6_test type vti6 remote…
When was CVE-2026-63917 disclosed?
CVE-2026-63917 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63917 actively exploited?
CVE-2026-63917 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.6% of all scored CVEs.
What is the CVSS score of CVE-2026-63917?
CVE-2026-63917 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63917?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63917, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63917

Explore →

Is Your Infrastructure Affected by CVE-2026-63917?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.