CVE-2026-46120
Last modified
CVE-2026-46120 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ip6_gre: Use cached t->net in ip6erspan_changelink(). After commit 5e72ce3e3980 ("net: ipv6: Use link netns in newlink() of rtnl_link_ops"), ip6erspan_newlink() correctly resolves the per-netns ip6gre hash via link_net. ip6erspan_changelink() was not converted in that series and still uses dev_net(dev), which diverges from the device's creation netns after IFLA_NET_NS_FD migration. This re-inserts the tunnel into the wrong per-netns hash. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ip6_gre: Use cached t->net in ip6erspan_changelink(). After commit 5e72ce3e3980 ("net: ipv6: Use link netns in newlink() of rtnl_link_ops"), ip6erspan_newlink() correctly resolves the per-netns ip6gre hash via link_net. ip6erspan_changelink() was not converted in that series and still uses dev_net(dev), which diverges from the device's creation netns after IFLA_NET_NS_FD migration. This re-inserts the tunnel into the wrong per-netns hash. The original netns keeps a stale entry. When that netns is later destroyed, ip6gre_exit_rtnl_net() walks the stale entry, producing a slab-use-after-free reported by KASAN, followed by a kernel BUG at net/core/dev.c (LIST_POISON1) in unregister_netdevice_many_notify(). Reachable from an unprivileged user namespace (unshare --user --map-root-user --net). ip6gre_changelink() earlier in the same file already uses the cached t->net; only ip6erspan_changelink() has the wrong shape.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.16.12, < 4.17 | — |
| Linux | Linux Kernel | >= 4.17.1, < 5.10.258 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.209 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.175 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.140 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.88 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.30 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.7 | — |
| Linux | Linux Kernel | 4.17 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Undergoing Analysis
Frequently Asked Questions
What is CVE-2026-46120?
How severe is CVE-2026-46120?
How do I fix CVE-2026-46120?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-46115In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-46116In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46117In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46118In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46119In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-4612A vulnerability has been found in itsourcecode Free Hotel Re…7.3
- CVE-2026-46121In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46122In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46123In the Linux kernel, the following vulnerability has been re…7.7
- CVE-2026-46124In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-46125In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-46126In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-46120?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
