[CVE-2026-74367][LOW] wifi: ath12k: fix inconsistent arvif state in vdev_create error paths [ Upstream

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

CVE: CVE-2026-74367
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: wifi: ath12k: fix inconsistent arvif state in vdev_create error paths [ Upstream
Commit: e0140e094b196d92f2a4ce167ee73cbfab000290
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e0140e094b196d92f2a4ce167ee73cbfab000290
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74367
Analysis date: Sat, 15 Aug 2026 20:20:21 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
ath12k vdev creation error paths could leave arvif and vdev bookkeeping inconsistent after WMI or peer cleanup failures, allowing later local privileged wireless management operations to hit driver failure or DoS, with no direct packet based reachability or demonstrated privilege escalation.

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

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

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-74367	LOW	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-703;CWE-665;CWE-459;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'ath12k_mac_vdev_create() had incomplete error handling in vdev creation and peer cleanup paths. A failed WMI vdev create or peer delete operation could leave arvif and vdev bookkeeping in an inconsistent state even though the firmware object was not created or was not fully rolled back. Later code can treat this stale state as a valid vdev and may hit driver failures or a crash. For the CVSS the PR:L is used for the paranoid score because a delegated CAP_NET_ADMIN user, container service, or network management process may be able to trigger wireless vdev creation paths without full host root. The issue is not directly network reachable through packet traffic and normally requires local control of wireless interface configuration. Impact is denial of service only based on the available patch evidence.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	REMOTE ERRORPATH NETWORK LINUS  LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

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

ActionableScore=2
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**

## 2. Signal breakdown

Conservative signals:

* Firmware-mediated external influence: +1. The bad state is reached when WMI or firmware-side vdev or peer operations fail.
* Availability impact realistic: +1. Inconsistent vdev/arvif bookkeeping can plausibly break later driver operations or cause device-level DoS.
* Requires admin/root/CAP_NET_ADMIN in typical deployments: -2. Creating or reconfiguring wireless vdev state normally requires privileged network administration.

Paranoid additional interpretation:

* Weak/indirect corruption candidate: +1. The rollback paths can leave stale logical state such as non-NULL arvif->ar, live vdev maps, counters, or list membership, but no concrete UAF, OOB write, double free, callback control, or attacker-controlled reclaim is shown.
* Reduced/delegated privilege interpretation: -1 instead of -2. In some systems, Wi-Fi management may be delegated to a service, container, or constrained CAP_NET_ADMIN context rather than full host root.

Not awarded:

* No remote/network-triggerable score. Packet traffic alone does not reach this control path.
* No generic strong memory corruption. The patch fixes inconsistent state and cleanup routing, not a demonstrated overwrite or lifetime reuse primitive.
* No privilege escalation plausible signal. There is no supported LPE primitive in the patch.

## 3. Reachability analysis

The likely trigger is local control of ath12k wireless interface creation or reconfiguration combined with firmware or WMI failure paths. In typical deployments this requires root or CAP_NET_ADMIN via tools such as hostapd, NetworkManager, iw, or driver management paths. A delegated network-management service or container with network administration capabilities may reduce the practical privilege requirement, but an ordinary remote attacker sending Wi-Fi or IP traffic is not shown to trigger this directly. The path is hardware and driver specific to ath12k and MLO-related vdev creation, so exposure depends on affected Qualcomm Wi-Fi hardware and configuration.

Call-site confidence: high for the changed error paths inside ath12k_mac_vdev_create. Medium for later consequences, because the patch describes stale readiness checks and inconsistent bookkeeping but does not include a concrete crash trace or memory corruption sink.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like driver robustness issue rather than an Important-class vulnerability. The theoretical concern is stale driver state after failed rollback, but realistic evidence supports local privileged or delegated-admin DoS rather than memory corruption or privilege escalation. The paranoid score keeps it nonzero because rollback bugs in device state can later cause crashes, but the evidence does not support Actionable Moderate handling.

## 5. One-sentence report phrase

ath12k vdev creation error paths could leave arvif and vdev bookkeeping inconsistent after WMI or peer cleanup failures, allowing later local privileged wireless management operations to hit driver failure or DoS, with no direct packet based reachability or demonstrated privilege escalation.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

The issue can be handled as low-priority unless the affected product delegates Wi-Fi vdev management to untrusted users or has evidence of a reproducible crash beyond the inconsistent state described here.

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

Patch: wifi: ath12k: fix inconsistent arvif state in vdev_create error paths [ Upstream
Commit: e0140e094b196d92f2a4ce167ee73cbfab000290
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e0140e094b196d92f2a4ce167ee73cbfab000290

Changed files:
  drivers/net/wireless/ath/ath12k/mac.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=e0140e094b196d92f2a4ce167ee73cbfab000290

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

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

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:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.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: 0
  Paranoid ActionableScore: 2

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