[CVE-2026-80641][LOW] wifi: wlcore: enable the right set of ciphers [ Upstream

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

CVE: CVE-2026-80641
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: wifi: wlcore: enable the right set of ciphers [ Upstream
Commit: ff9748200698e9641f41ba922ffef728167807c2
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ff9748200698e9641f41ba922ffef728167807c2
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80641
Analysis date: Fri, 28 Aug 2026 04:21:08 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: YES

Summary:
wlcore may repeatedly attempt to use an unsupported IGTK related cipher on affected firmware during WiFi association, causing key setup failure and an endless hardware recovery loop with loss of wireless connectivity.

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

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

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: YES

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

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

CVE-2026-80641	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L';CWE-682;CWE-697;CWE-754;Other CVSS 'AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L';BEST CVSS score: '4.3';DESCR 'wlcore can advertise or keep trying to use an unsupported IGTK related cipher on affected firmware and wl12xx devices, which can make key installation fail during WiFi association. This can trigger repeated hardware recovery and warning paths, causing loss of WiFi connectivity or driver instability rather than memory corruption. For the CVSS the PR:N because a nearby access point or wireless peer does not need local privileges on the target, although the target must use the affected wlcore hardware and attempt association. The vector is adjacent network rather than Internet reachable. Impact is denial of service limited to the wireless device or networking function, with no evidence of confidentiality impact, integrity impact, UAF, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)  SKIP CVE-2026-80641 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE NETWORK HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

## 1. ActionableScore

ActionableScore=2
ActionableScoreLower=1

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

## 2. Signal breakdown

* +1 Firmware-mediated external influence: the failure depends on wlcore firmware capability handling and can be exposed during WiFi association with an AP.
* +1 Availability impact realistic: affected devices can enter repeated hardware recovery, causing loss of WiFi connectivity.
* -1 Rare and difficult-to-reach subsystem/configuration: this affects specific TI wlcore hardware or firmware combinations, especially wl12xx or older firmware.
* Paranoid +1 limited reliable device DoS: the commit says the recovery sequence repeats endlessly, so a stronger device-level availability interpretation is defensible.

Not applied:

* No generic memory corruption: the patch adjusts cipher capability accounting and does not show UAF, OOB write, double free, refcount misuse, or type confusion.
* No privilege escalation plausible: there is no supported path from the patch to LPE.
* No confidentiality or integrity impact: the visible impact is failed key setup and recovery loop, not data disclosure or unauthorized modification.
* No common networking core path bonus: this is a device-specific WiFi driver capability bug, not a central packet-processing path.

## 3. Reachability analysis

A nearby wireless AP or wireless environment can plausibly trigger the bad path when the affected client attempts association and the driver tries to configure unsupported IGTK related key material. For the CVSS the PR:N because the external wireless peer does not need local privileges on the target system, but the target must have affected wlcore hardware and must attempt to connect. This is adjacent network reachability, not Internet reachability.

Namespaces and containers do not materially change the risk because the vulnerable path is tied to physical WiFi hardware and driver firmware behavior. The issue is not broadly default-exposed on servers and depends on specific TI wlcore devices and firmware versions. Call-site confidence: high, because the patch and commit message show the relevant initialization path and the repeated recovery symptom.

## 4. Severity interpretation

This behaves like a Low or ordinary Moderate availability issue rather than an Important-class kernel vulnerability. The realistic impact is loss of WiFi functionality or repeated driver recovery on affected hardware. Theoretical memory corruption potential is not supported by the patch. There is no evidence of attacker-controlled kernel memory reuse, write primitive, information leak, or privilege escalation.

## 5. One-sentence report phrase

wlcore may repeatedly attempt to use an unsupported IGTK related cipher on affected firmware during WiFi association, causing key setup failure and an endless hardware recovery loop with loss of wireless connectivity.

## 6. Manual review recommendation

NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED

Reason: this is a hardware and firmware compatibility availability issue with no demonstrated memory corruption, no LPE path, no confidentiality or integrity impact, and limited adjacent-network exposure.

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

Patch: wifi: wlcore: enable the right set of ciphers [ Upstream
Commit: ff9748200698e9641f41ba922ffef728167807c2
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ff9748200698e9641f41ba922ffef728167807c2

Changed files:
  drivers/net/wireless/ti/wlcore/main.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=ff9748200698e9641f41ba922ffef728167807c2

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

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

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