[CVE-2026-98073][LOW] net: Remove conflicting altnames for dying netns in __dev_change_net_namespace(). [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-98073
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: net: Remove conflicting altnames for dying netns in __dev_change_net_namespace(). [ Upstream
Commit: a29ea5b5034654aaaa4aadd771f48c01abfd2dfa
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a29ea5b5034654aaaa4aadd771f48c01abfd2dfa
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98073
Analysis date: Fri, 25 Sep 2026 09:21:59 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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: LOW
Manual review required: NO

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

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

CVE-2026-98073	LOW	https://www.kernelcve.org/list/?q=CVE-2026-98073 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:U/C:N/I:N/A:L';CWE-703;CWE-670;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N';BEST CVSS score: '3.3';DESCR 'A logic error in network namespace cleanup can cause __dev_change_net_namespace to reject a device move when an alternative interface name conflicts with a name in init_net. A local process can create devices in separate network namespaces with the same alternative name and then destroy the non root namespace, causing a cfg80211 or cfg802154 cleanup warning. For the CVSS the PR:L reflects that reliable triggering requires local namespace and network device configuration capabilities. The issue is not network reachable and the available evidence indicates a warning and cleanup failure scenario rather than memory corruption, information disclosure, privilege escalation, or a kernel crash. Impact is normally limited to logging and cleanup path disruption.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0)	YES	REMOTE DANGER INIT HARDWARE SYZBOT  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	NO	NO	checked

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

ActionableScore=0
PrimitiveClass=NONE
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 0
* Conservative score: 0
* Raw paranoid score: 0
* Paranoid score: 0
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +0: The patch establishes an alternative interface name conflict during network namespace cleanup. It does not establish a UAF, stale dereference, double release, refcount mutation, OOB access, invalid write, information disclosure, or authorization bypass.
* +0: The demonstrated result is WARN in cfg80211_pernet_exit while cleanup_net processes a dying network namespace. WARN alone is not a kernel crash or independently scored availability impact.
* +0: No remote reachability is established. The trigger is a local network namespace and netdevice configuration sequence.
* +0: No controlled reclaim, arbitrary write, structured stale-object leverage, confidentiality impact, integrity impact, privilege escalation, or security-boundary bypass is demonstrated.
* +0: No negative privilege penalty is applied. The supplied context does not prove that host-admin-equivalent privilege is required for the complete sequence, but it also does not prove complete below-host-admin reachability.

3. Reachability analysis

The reported sequence creates devices in the root and non-root network namespaces, assigns the same alternative name, and destroys the non-root namespace. Setting alternative interface names and creating or configuring the relevant devices normally involves CAP_NET_ADMIN checks, but the supplied patch does not show which user namespace governs every required operation.

A non-root network namespace alone does not prove that an ordinary unprivileged user can complete the full trigger against the relevant root namespace device state. In particular, the reproducer requires a conflicting name in init_net or another target namespace involved in device migration. Therefore HostAdminRequired and NamespaceScopedPrivilege remain UNKNOWN.

No network packet path, external device input, firmware input, special hardware, race window, or prior privileged setup is established as part of the vulnerability itself.

4. Primitive and severity interpretation

The exact defect is a cleanup-state logic error. During migration of a network device from a dying namespace, __dev_change_net_namespace rejected a conflicting alternative name instead of removing that conflicting alternative name. This caused cfg80211_pernet_exit or cfg802154_pernet_exit to emit a warning during namespace cleanup.

This is neither active structured-object lifetime corruption nor fixed stale storage. There is no release, put, free, refcount operation, stale pointer use, or second lifetime mutation. The patch changes conflict handling for netdev alternative names and preserves the normal rejection behavior when the source namespace is still live.

PrimitiveClass is NONE. The demonstrated consequence is cleanup warning and possible cleanup-path disruption. A kernel crash, persistent resource loss, disclosure, integrity modification, privilege escalation, or meaningful security-boundary bypass is not established. ImportantCandidate is NO and AutoDowngradeAllowed is YES because no unresolved corruption or authorization primitive remains.

5. One-sentence report phrase

A conflicting netdev alternative name could cause a warning during cfg80211 or cfg802154 network namespace cleanup, with no demonstrated memory corruption, privilege escalation, or kernel crash.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

The patch addresses a WARN-only cleanup logic defect with no demonstrated security-relevant primitive.

7. Call-site confidence

Call-site confidence: high

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

Patch: net: Remove conflicting altnames for dying netns in __dev_change_net_namespace(). [ Upstream
Commit: a29ea5b5034654aaaa4aadd771f48c01abfd2dfa
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a29ea5b5034654aaaa4aadd771f48c01abfd2dfa

Changed files:
  net/wireless/core.c
  net/core/net_namespace.c
  kernel/workqueue.c
  kernel/kthread.c
  arch/x86/kernel/process.c
  arch/x86/entry/entry_64.S
  net/core/dev.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=a29ea5b5034654aaaa4aadd771f48c01abfd2dfa

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

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

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:L/PR:L/UI:N/S:U/C:N/I:N/A:N
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS score: 3.3

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: unknown
  Paranoid ActionableScore: 0

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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