In the Linux kernel, the following vulnerability has been resolved: ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate(). (CVE-2026-63921)
A vulnerability in the Linux kernel's IPv6 virtual tunnel interface (vti) was resolved by correcting the network namespace used during tunnel device lookups in the vti6_siocdevprivate() function. The issue allowed a migrated tunnel device to be incorrectly linked in the original network namespace's hash, potentially enabling packet delivery through a device controlled by an attacker. The fix ensures lookups use the correct network namespace and adds capability checks to prevent unauthorized manipulation.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel involved the vti6_siocdevprivate() function using dev_net(dev) for tunnel device collision lookups after a tunnel had been migrated to a different network namespace via IFLA_NET_NS_FD. This caused lookups to fail in the migrated namespace and incorrectly insert the migrated tunnel device into the creation namespace's hash bucket. Consequently, packets could be delivered through a device controlled by an attacker in a different network namespace. The patch changes the lookup to use t->net (the tunnel's original network namespace) and adds a capability check requiring CAP_NET_ADMIN in the creation namespace's user namespace, preventing unprivileged users from exploiting this cross-namespace tunnel manipulation.
Potential Impact
An attacker with access to an unprivileged user namespace and network namespace (e.g., via unshare with user and net namespaces) could manipulate IPv6 virtual tunnel devices to cause packet delivery through a device they control in a different network namespace. This represents a cross-tenant scope issue on container hosts, potentially allowing unauthorized packet interception or redirection across network namespaces.
Mitigation Recommendations
A patch has been applied to the Linux kernel that corrects the network namespace used in tunnel device lookups and adds capability checks requiring CAP_NET_ADMIN in the relevant user namespace. Users should update to a Linux kernel version that includes this fix once available. Until then, restricting unprivileged user namespace and network namespace creation can reduce exposure. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate(). (CVE-2026-63921)
Description
A vulnerability in the Linux kernel's IPv6 virtual tunnel interface (vti) was resolved by correcting the network namespace used during tunnel device lookups in the vti6_siocdevprivate() function. The issue allowed a migrated tunnel device to be incorrectly linked in the original network namespace's hash, potentially enabling packet delivery through a device controlled by an attacker. The fix ensures lookups use the correct network namespace and adds capability checks to prevent unauthorized manipulation.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel involved the vti6_siocdevprivate() function using dev_net(dev) for tunnel device collision lookups after a tunnel had been migrated to a different network namespace via IFLA_NET_NS_FD. This caused lookups to fail in the migrated namespace and incorrectly insert the migrated tunnel device into the creation namespace's hash bucket. Consequently, packets could be delivered through a device controlled by an attacker in a different network namespace. The patch changes the lookup to use t->net (the tunnel's original network namespace) and adds a capability check requiring CAP_NET_ADMIN in the creation namespace's user namespace, preventing unprivileged users from exploiting this cross-namespace tunnel manipulation.
Potential Impact
An attacker with access to an unprivileged user namespace and network namespace (e.g., via unshare with user and net namespaces) could manipulate IPv6 virtual tunnel devices to cause packet delivery through a device they control in a different network namespace. This represents a cross-tenant scope issue on container hosts, potentially allowing unauthorized packet interception or redirection across network namespaces.
Mitigation Recommendations
A patch has been applied to the Linux kernel that corrects the network namespace used in tunnel device lookups and adds capability checks requiring CAP_NET_ADMIN in the relevant user namespace. Users should update to a Linux kernel version that includes this fix once available. Until then, restricting unprivileged user namespace and network namespace creation can reduce exposure. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-c82w-wxq7-hwv4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63921"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ab2a4a8d598912f23b
Added to database: 07/19/2026, 19:38:19 UTC
Last enriched: 07/19/2026, 20:07:28 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.