cve.bz

CVE-2026-63914 linux linux kernel: Exposure of Resource to Wrong Sphere

7.3 highEPSS 0.1%Fix available

High (7.3) in linux linux kernel. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: xfrm: route MIGRATE notifications to caller's netns xfrm_send_migrate() in net/xfrm/xfrm_user.c and pfkey_send_migrate() in net/key/af_key.c both hardcode &init_net for the multicast that announces a successful XFRM_MSG_MIGRATE / SADB_X_MIGRATE. XFRM_MSG_MIGRATE arrives on a per-netns NETLINK_XFRM socket, and the rest of the xfrm/af_key netlink path was made netns-aware in 2008. The other 14 multicast paths in xfrm_user.c route their event using xs_net(x), xp_net(xp) or sock_net(skb->sk); only the migrate path was missed. Two consequences of the init_net hardcoding: 1. The notification (selector, old/new endpoint addresses, and the km_address) is delivered to listeners on init_net's XFRMNLGRP_MIGRATE / pfkey BROADCAST_ALL groups rather than on the issuing netns. An IKE daemon running in init_net therefore receives migration notifications originating from any other netns on the host. 2. An IKE daemon running inside a non-init netns and subscribed to its own XFRMNLGRP_MIGRATE / pfkey groups never receives the notification of its own migration. IKEv2 MOBIKE / address-update handling inside a netns is silently broken. Thread struct net through km_migrate() and the xfrm_mgr.migrate function pointer, drop the &init_net override in xfrm_send_migrate() and pfkey_send_migrate(), and pass the caller's net (already in scope in xfrm_migrate() via sock_net(skb->sk)) all the way down. struct xfrm_mgr is in-tree only and not exported as a stable API, so the function-pointer signature change is internal. pfkey_broadcast() is already netns-aware via net_generic(net, pfkey_net_id) since the pernet conversion. The five other pfkey_broadcast() callers in af_key.c already pass xs_net(x), sock_net(sk) or a per-netns net, so this only removes the &init_net outlier.

Severity

CVSS 3.1

7.3 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-668 Exposure of Resource to Wrong Sphere
CWE-862 Missing Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-63914 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63914?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63914?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63914 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux2.6.21 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.259
Linux5.155.15.210
Linux6.16.1.176
Linux6.66.6.143
Linux6.126.12.93
Linux6.186.18.35
Linux7.07.0.12
Linuxlater releases7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.176-1DEBIAN-CVE-2026-63914
Debian13linux6.12.94-1DEBIAN-CVE-2026-63914
Debian14linux7.0.12-1DEBIAN-CVE-2026-63914
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-63914
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-63914
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-63914
Ubuntu22.04:LTSlinux5.15.0-198.208UBUNTU-CVE-2026-63914 USN-8875-1
Ubuntu22.04:LTSlinux-aws5.15.0-1117.124UBUNTU-CVE-2026-63914 USN-8875-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1066.69~22.04.1UBUNTU-CVE-2026-63914 USN-8903-1
Ubuntu22.04:LTSlinux-azure5.15.0-1123.132UBUNTU-CVE-2026-63914 USN-8875-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1122.131UBUNTU-CVE-2026-63914
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1068.75~22.04.1UBUNTU-CVE-2026-63914 USN-8904-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1118.128UBUNTU-CVE-2026-63914 USN-8877-1
Ubuntu22.04:LTSlinux-gcp-6.8, linux-azure-6.86.8.0-1070.78~22.04.1UBUNTU-CVE-2026-63914 USN-8904-1 USN-8905-1
Ubuntu22.04:LTSlinux-gke5.15.0-1113.119UBUNTU-CVE-2026-63914 USN-8875-1
80 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:10.3rv, perf, rtla and 89 more0:6.12.0-264.9.1.el10_3RHSA-2026:97040
Alpaquita23linux-lts6.1.177-r0BELL-CVE-2026-63914
Alpaquita25linux-lts6.12.95-r0BELL-CVE-2026-63914
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-63914

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

XFRM MIGRATE notifications were multicast in init_net even when the migration request originated from a different network namespace. This can expose IPsec migration metadata such as selectors, old and new endpoint addresses, and km_address to listeners in init_net, while the IKE daemon inside the originating namespace may miss its own migration event. For the CVSS the PR:L is used in the paranoid score because a reduced capability container root or delegated service account with CAP_NET_ADMIN in its own network namespace may be able to trigger the affected control plane path. The issue is not directly network reachable and is not a memory corruption bug. Impact is mainly namespace isolation bypass, limited confidentiality exposure, possible limited integrity confusion in user space IKE handling, and availability impact for MOBIKE or address update handling inside non init namespaces.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelAffected
Red Hat Enterprise Linux 7kernel-rtAffected
Red Hat Enterprise Linux 8kernelAffected
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-63914.

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON