# CVE-2026-63829: net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink

> Attackers with limited network namespace privileges can modify GRE tunnels in other namespaces due to missing capability checks.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-92588, BELL-CVE-2026-63829, DEBIAN-CVE-2026-63829, GHSA-6wc5-2mjj-pmr6, ROOT-OS-DEBIAN-11-CVE-2026-63829, ROOT-OS-DEBIAN-12-CVE-2026-63829, ROOT-OS-UBUNTU-2204-CVE-2026-63829, UBUNTU-CVE-2026-63829

## What is CVE-2026-63829?

CVE-2026-63829 is a high-severity missing authorization vulnerability in Linux kernel, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-63829?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-63829?

Apply the vendor's patch.

## Is CVE-2026-63829 being exploited?

There is no known exploitation of CVE-2026-63829 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63829 and fix it if it is affected.

What it is: CVE-2026-63829 is a high-severity missing authorization vulnerability in Linux kernel, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63829 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63829/ (Markdown: https://insights.sbomify.com/CVE-2026-63829/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63829
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63829
- OSV: https://osv.dev/vulnerability/CVE-2026-63829

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63829/
Summaries are generated and may contain mistakes; the official description above is the record.