CVE-2026-68432

vxlan: require CAP_NET_ADMIN in the device netns for changelink

HIGH
8.8
CVSS Score
Published: August 12, 2026 at 12:07 AM UTC
Updated: October 19, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: vxlan: require CAP_NET_ADMIN in the device netns for changelink A tunnel changelink() operates on at most two netns, dev_net(dev) and the sticky underlay netns vxlan->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 vxlan->net can rewrite a vxlan device whose underlay lives in vxlan->net. vxlan_changelink() validates and applies the new configuration against vxlan->net (vxlan_config_validate(vxlan->net, ...)) and can reopen the underlay socket in that netns, so the same reasoning as the tunnel changelink series applies here. Gate vxlan_changelink() with rtnl_dev_link_net_capable(), at the top of the op before any attribute is parsed, matching ipgre_changelink() and the rest of the "require CAP_NET_ADMIN in the device netns for changelink" series. Found by 0sec automated security-research tooling (https://0sec.ai).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.118bcdc4f3a20be949df54b67e5ae2734daabb5792
Vendor states this is fixed in 0aa580a8bbbed2507b4582a1f0ef581d480d06ed (fixed)
Vendor states this is fixed in 32d10c46bfde3e9b274e9e1bd6399d0ebea8f60f (fixed)
Vendor states this is fixed in 3a61bd9637f3d929aa846e4eb3d98b48c26fcb0e (fixed)
Vendor states this is fixed in 730c7e5fea7f06e0cdf21c547222ec93234fd1d6 (fixed)
Vendor states this is fixed in 7465ade989ba84adc2bfa58bad3ca25d249f0f7a (fixed)
Vendor states this is fixed in b3793d7dccb192ffff29894d11824db6251acdd5 (fixed)
Vendor states this is fixed in b95a8743e58f7efed5ddc4cb73829b66f17feab0 (fixed)
Vendor states this is fixed in e8ad0d311e225939a9a6c745d6cc384c7364ec87 (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-863

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card