CVE-2026-63829

CVE CVE-2026-63829EUVD EUVD-2026-45495Published 2026-07-19T12:02:23.000ZLast changed 2026-08-05T12:36:12.000ZCVSS 8.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink A tunnel changelink() operates on at most two netns, dev_net(dev) and the tunnel link netns t->net. They differ once the device is created in or moved to a netns other than the one the request runs in. The rtnl changelink path checks CAP_NET_ADMIN only against dev_net(dev), so a caller privileged there but not in t->net can rewrite a tunnel that lives in t->net. Add rtnl_dev_link_net_capable() next to rtnl_get_net_ns_capable() in net/core/rtnetlink.c. It requires CAP_NET_ADMIN in the link netns and is skipped when the link netns is dev_net(dev), where the rtnl path already checked it. The other patches in this series use the same helper. Gate ipgre_changelink() and erspan_changelink() with it, at the top of the op before any attribute is parsed, because the parsers update live tunnel fields first. ipgre_netlink_parms() sets t->collect_md before ip_tunnel_changelink() runs. Commit 8b484efd5cb4 ("ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().") added the same check on the ioctl path. This adds it on RTM_NEWLINK.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 0; b57708add31494175be741ed3fd24023b50c3423 <e54c05ed3d9c28733fb9e5837219aca3691defa3; 3.16; b57708add31494175be741ed3fd24023b50c3423 <8165f7ff57d9667d2bb477ef6af83ede7fed4ad7; patch: 7.2-rc1; b57708add31494175be741ed3fd24023b50c3423 <1697957eb0971d420dde42862b88eb43506a1105; b57708add31494175be741ed3fd24023b50c3423 <19275943d8fe903eb7b9aa53e380e41efd042ada; patch: 7.1.3; b57708add31494175be741ed3fd24023b50c3423 <9831bc9ecb402957810c2045c663fbfe9b09e296; patch: 5.15.212; b57708add31494175be741ed3fd24023b50c3423 <866b0f5ae599490bd496fd84581c68ac8b94e6af; patch: 5.10.261; patch: 6.12.95; patch: 6.18.38; patch: 6.6.145; b57708add31494175be741ed3fd24023b50c3423 <92b766fc55156e0da2ecd0c2302c971118f8a229; patch: 6.1.178; b57708add31494175be741ed3fd24023b50c3423 <47b5d3d506609b08b2e1f7c14f0b681a1953d572

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.