Vulnerability · CVE-2026-63914
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…
Published Jul 19, 2026 · catalog updated Oct 30, 2026 · linux kernel
Last checked Oct 31, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-63914. EPSS is 0.15%. Act only if a listed version of linux kernel is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-100073 · Medium
- CVE-2026-100072 · High
- CVE-2026-100071 · Medium
- CVE-2026-100070 · Medium
- CVE-2026-98159 · Medium
- Severity
- High7.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.15%
- Remediation
- Version ranges on file
- Affected products
- cpe linux/linux kernel
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe linux/linux kernel7.1
- cpe linux/linux kernel< 5.10.259
- cpe linux/linux kernel< 5.15.210
- cpe linux/linux kernel< 6.1.176
- cpe linux/linux kernel< 6.12.93
- cpe linux/linux kernel< 6.18.35
- cpe linux/linux kernel< 6.6.143
- cpe linux/linux kernel< 7.0.12
How to fix CVE-2026-63914
Upgrade
CVE-2026-63914 lists a fix boundary at 5.10.259. Compare the installed build with that boundary before you change production.
Version check
Affected < 5.10.259
Advisory
Open the bsi record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-63914. EPSS is 0.15%. Act only if a listed version of linux kernel is installed.
Which versions are affected?
Compare what you have installed with linux/linux kernel 7.1; linux/linux kernel < 5.10.259; linux/linux kernel < 5.15.210; linux/linux kernel < 6.1.176. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-668: Exposure of Resource to Wrong Sphere; CWE-862: Missing Authorization. EPSS 0.15%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 26, 2026 · BSI CERT-Bund
Detected
CVE-2026-63914 is listed by Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff.
Oct 30, 2026 · NIST NVD
Updated
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/
Sources
- BSI CERT-BundGovernment advisoryCVE-2026-63914
Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff
wid.cert-bund.de - CVE.orgVulnerability recordCVE-2026-63914
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-63914
30-day exploitation probability 0.15%
first.org - NIST NVDVulnerability recordCVE-2026-63914
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
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- NIST NVDOct 31, 2026
- FIRST EPSSOct 29, 2026
- CVE.orgOct 27, 2026
- BSI CERT-BundOct 27, 2026