[CVE-2026-72054][IMPORTANT] net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink

[CVE-2026-72054][IMPORTANT] net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink

[AL-KERNEL]

CVE: CVE-2026-72054
Priority: IMPORTANT
AL-KERNEL base severity: IMPORTANT
KPANIC flag: YES
Patch: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink
Commit: 1caf737e625143c6f23c32d2b747b1a3e42e5699
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1caf737e625143c6f23c32d2b747b1a3e42e5699
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72054
Analysis date: Sun, 16 Aug 2026 09:21:16 -0400
ActionableScore: 6
ActionableScore lower bound: 5
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
A missing CAP_NET_ADMIN check in the VTI tunnel link namespace allows a caller privileged only in dev_net(dev) to rewrite a tunnel belonging to another network namespace, causing a cross-netns authorization bypass with possible tunnel policy changes or disruption.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72054 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72054

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: IMPORTANT
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-72054	IMPORTANT	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H';CWE-862;CWE-284;CWE-269;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L';BEST CVSS score: '8.7';DESCR 'vti_changelink could modify a VTI tunnel that belongs to t net when the caller only has CAP_NET_ADMIN in dev_net(dev). This creates a cross namespace authorization bypass after a VTI device is created in or moved to a different network namespace than the request context. For the CVSS the PR:L is used for the paranoid score because CAP_NET_ADMIN in a reduced namespace, container root, or delegated network admin context is not equivalent to full host administrator control. The issue is not directly network reachable and is triggered through local rtnetlink control plane operations. Impact can include unauthorized tunnel parameter changes, traffic redirection, policy bypass, or tunnel disruption across namespace boundaries.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 7)	YES	REMOTE SIMPLEFIX NETWORK HARDWARE KPANIC  KPANIC INCREASED_TO_HIGH_BASED_ON_GUESSCVSS	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=6
ActionableScoreLower=5

## 1. ActionableScore

* Conservative score: 5
* Paranoid score: 6
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

* Security-boundary bypass with practical sensitive-object access: +2
  The bug bypasses the intended CAP_NET_ADMIN check for the tunnel link network namespace. A caller privileged only in dev_net(dev) can modify a VTI tunnel belonging to t->net.

* Cross-boundary isolation/policy bypass: +1
  This is a network namespace boundary violation. It can affect objects outside the namespace where the caller is authorized.

* Integrity impact plausible: +1
  Unauthorized tunnel parameter changes can alter routing, tunnel endpoints, keys or marks, and network policy behavior.

* Availability impact realistic: +1
  A rewritten VTI tunnel can disrupt connectivity or break tunnel operation across namespace boundaries.

* Confidentiality impact plausible in paranoid scoring: +1
  If tunnel changes allow traffic redirection or policy bypass, limited confidentiality exposure is plausible, although this is deployment dependent and not a direct memory disclosure primitive.

* Requires elevated but reduced privilege: 0
  The attacker needs CAP_NET_ADMIN in one namespace, but the bug is that this capability is incorrectly accepted for a different namespace. This should not receive the full admin penalty because it breaks a capability and namespace separation model.

* No memory corruption: +0
  The patch is an authorization check. There is no UAF, OOB access, double free, type confusion, or arbitrary write primitive.

* Not directly network reachable: +0
  The trigger is rtnetlink changelink control plane activity, not packet processing.

## 3. Reachability analysis

The issue is locally triggerable by a process that can perform rtnetlink changelink operations with CAP_NET_ADMIN in dev_net(dev), while lacking CAP_NET_ADMIN in the tunnel link namespace t->net. This is most relevant for containers, network namespaces, delegated network administration, or reduced-capability root contexts. It is not directly reachable by remote packets. The affected path is configuration dependent because VTI devices and namespace movement or creation across namespaces are required, but this is a normal Linux networking feature rather than a rare debug mode.

Call-site confidence: high. The patch directly modifies vti_changelink(), and the commit explains the missing capability check and the two namespace relationship.

## 4. Severity interpretation

This behaves more like an actionable Moderate or Important candidate than an ordinary Moderate. The impact is not memory corruption or kernel code execution. The important security property is namespace and capability isolation. A caller authorized in one network namespace can modify tunnel state in another namespace, which may cause unauthorized policy changes, traffic disruption, or traffic redirection. The conservative score treats this as a serious local capability-boundary bypass. The paranoid score adds limited confidentiality concern because VTI tunnel rewriting can plausibly affect traffic visibility or routing in some deployments.

## 5. One-sentence report phrase

A missing CAP_NET_ADMIN check in the VTI tunnel link namespace allows a caller privileged only in dev_net(dev) to rewrite a tunnel belonging to another network namespace, causing a cross-netns authorization bypass with possible tunnel policy changes or disruption.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED.
YES REQUIRES MANUAL CHECK.

Reason: this is a namespace and capability boundary bypass, not a simple local admin-only configuration bug. The real impact depends on container or delegated CAP_NET_ADMIN deployment models and on whether the affected VTI tunnel carries sensitive or production traffic.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink
Commit: 1caf737e625143c6f23c32d2b747b1a3e42e5699
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1caf737e625143c6f23c32d2b747b1a3e42e5699

Commit description:

vti_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.

Gate vti_changelink() on rtnl_dev_link_net_capable() at its top,
before any attribute is parsed.

Reported-by: Xiao Liang <shaw.leon@gmail.com>
Closes: https://lore.kernel.org/netdev/CABAhCOSzP1vaThGV35_VnsRCb=87_CPjPVsTHbq905k8A+BuUg@mail.gmail.com/
Fixes: 895de9a ("vti4: Enable namespace changing")
Cc: stable@vger.kernel.org
Signed-off-by: Maoyi Xie <maoyixie.tju@gmail.com>
Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>
Link: https://patch.msgid.link/20260612085941.3158249-4-maoyixie.tju@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  net/ipv4/ip_vti.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1caf737e625143c6f23c32d2b747b1a3e42e5699

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72054 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72054

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H
  The Best / paranoid CVSS score: 8.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 5
  Paranoid ActionableScore: 6

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: IMPORTANT
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): IMPORTANT

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).