CVE-2026-46120: ip6_gre: Use cached t->net in ip6erspan_changelink().

Published May 28, 2026
·
Updated

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

ip6gre: Use cached t->net in ip6erspanchangelink().

After commit 5e72ce3e3980 ("net: ipv6: Use link netns in newlink() of rtnllinkops"), ip6erspannewlink() correctly resolves the per-netns ip6gre hash via linknet. ip6erspanchangelink() was not converted in that series and still uses devnet(dev), which diverges from the device's creation netns after IFLANETNSFD 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, ip6greexitrtnlnet() walks the stale entry, producing a slab-use-after-free reported by KASAN, followed by a kernel BUG at net/core/dev.c (LISTPOISON1) in unregisternetdevicemanynotify().

Reachable from an unprivileged user namespace (unshare --user --map-root-user --net).

ip6grechangelink() earlier in the same file already uses the cached t->net; only ip6erspanchangelink() has the wrong shape.

Affected Software

14 affected componentsFixes available
Linux Linux kernel
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=4.17-rc7
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Microsoft azl3 kernel 6.6.139.1-1<6.6.141.1-1
6.6.141.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.141.1-1

Event History

May 28, 2026
CVE Published
via MITRE·09:35 AM
Data Sourced
via MITRE·09:35 AM
DescriptionSeverity
Data Sourced
via NVD·10:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·11:05 AM
DescriptionSeverityAffected Software
May 29, 2026
Data Sourced
via Microsoft·08:07 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who can realistically trigger this issue?

The issue is reachable from an unprivileged user namespace. The described path uses unshare --user --map-root-user --net, so systems that permit unprivileged user and network namespace creation are exposed to that attack path.

2

What conditions are needed to trigger the use-after-free?

An IP6 ERSPAN tunnel must be migrated using IFLA_NET_NS_FD and then changed through ip6erspan_changelink(). The original network namespace must later be destroyed, causing cleanup to walk the stale tunnel entry.

3

How can I recognize that this issue may already have occurred?

The reported failure pattern is a KASAN slab-use-after-free during network-namespace teardown, followed by a kernel BUG at net/core/dev.c involving LIST_POISON1 in unregister_netdevice_many_notify().

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203