[CVE-2026-80722][MODERATE 7.0] wifi: mac80211: validate individual TWT params before driver setup [ Upstream

[CVE-2026-80722][MODERATE 7.0] wifi: mac80211: validate individual TWT params before driver setup [ Upstream

[AL-KERNEL]

CVE: CVE-2026-80722
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: wifi: mac80211: validate individual TWT params before driver setup [ Upstream
Commit: 92fcd0f30dc8e51f252589b082d46851d295cc1a
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=92fcd0f30dc8e51f252589b082d46851d295cc1a
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80722
Analysis date: Fri, 28 Aug 2026 06:36:19 -0400
ActionableScore: 6
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A short individual S1G TWT setup frame can reach the mac80211 driver setup path with incomplete ieee80211_twt_params data, allowing an adjacent Wi-Fi attacker with PR:N to cause OOB parameter consumption and possible driver-dependent DoS or limited C/I impact.

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

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

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: MODERATE 7.0
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-80722	MODERATE	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:L/I:L/A:H';CWE-125;*CWE-20;CWE-126;Other CVSS 'AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L';BEST CVSS score: '7.6';DESCR 'A short individual S1G TWT setup frame can reach ieee80211_s1g_rx_twt_setup() with a length that is too small for the full ieee80211_twt_params block. The individual path then passes the TWT data to drv_add_twt_setup(), while the tracepoint and driver callback may consume the complete parameter block and read beyond the validated frame contents. For the CVSS the PR:N is used because the attacker does not need local privileges on the victim and only needs radio reachability to the affected Wi-Fi interface. The vector is AV:A rather than AV:N because exploitation requires 802.11 adjacency and is not a normal routed network attack. Impact is at least adjacent-network denial of service risk and possible limited confidentiality or integrity impact from out-of-bounds reads or driver-dependent handling, so this should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	REMOTE SIMPLEFIX KPANIC  KPANIC INCREASED_TO_MODERATE7_BASED_ON_GUESSCVSS	NO	NO	checked

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

ActionableScore=6
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 6
* Final recommended bucket: **Actionable Moderate at minimum**

## 2. Signal breakdown

Conservative signals:

* Remote reachable / network-triggerable: +2. The input is a received Wi-Fi S1G TWT action frame, so the trigger is adjacent-network reachable over 802.11 radio, not local code execution.
* Confidentiality impact plausible: +1. The short frame can cause code to consume fields beyond the validated TWT parameter length, which is best treated as an OOB read candidate.
* Availability impact realistic: +1. Driver or tracepoint consumption of incomplete parameters can plausibly cause a driver-side fault or kernel warning/crash path.
* Rare AND difficult-to-reach subsystem/configuration: -1. The affected path depends on S1G TWT individual agreement support in AP mode, which is less common than ordinary Wi-Fi receive paths.
* Broad/default/common subsystem exposure: +1. mac80211 is a broadly deployed kernel Wi-Fi subsystem, even if this exact S1G/TWT mode is configuration-dependent.

Paranoid additional signals:

* Weak/indirect corruption candidate: +1. The driver callback receives an under-validated structure and may interpret missing fields as valid parameters, but the patch does not show an OOB write, UAF, reclaim primitive, or controlled overwrite.
* Reliable kernel crash / strong DoS: +1. For triage sensitivity, driver-dependent consumption of a short management frame can reasonably be treated as a strong DoS concern, especially because the bad data crosses from mac80211 validation into driver setup.
* Integrity impact plausible: +1. Limited integrity impact is possible if unvalidated or out-of-frame TWT fields influence driver configuration, but there is no evidence of arbitrary kernel memory modification.
* Cap rationale. This should not be raised to Important solely from the patch because the demonstrated primitive is short-frame validation failure with OOB read or invalid parameter consumption, not strong memory corruption.

## 3. Reachability analysis

An attacker does not need local privileges on the victim. The realistic attacker position is radio adjacency to an affected Wi-Fi interface that processes S1G TWT setup action frames. This is not AV:N Internet-style reachability, but it is network-triggerable in the adjacent 802.11 sense.

Namespaces and containers are not the main boundary here because the trigger is external wireless frame input. Practical exposure depends on hardware, driver support, AP mode, S1G support, and whether individual TWT support is enabled and reachable.

## 4. Severity interpretation

This behaves above ordinary Moderate because it is externally triggerable over Wi-Fi adjacency and passes under-validated frame data into driver setup logic. The realistic evidence supports OOB read or invalid parameter consumption with DoS risk.

It does not yet reach a strong Important classification because the patch does not show UAF, double-free, OOB write, arbitrary write, refcount takeover, callback control, or attacker-controlled object replacement. The paranoid score is kept as Actionable Moderate to avoid auto-closing a network-adjacent parser bug that enters driver code.

## 5. One-sentence report phrase

A short individual S1G TWT setup frame can reach the mac80211 driver setup path with incomplete ieee80211_twt_params data, allowing an adjacent Wi-Fi attacker with PR:N to cause OOB parameter consumption and possible driver-dependent DoS or limited C/I impact.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED.
YES REQUIRES MANUAL CHECK.

Reason: the bug is adjacent-network reachable, affects mac80211 frame parsing, and passes under-validated data into driver callbacks. Manual review should confirm whether any affected driver turns the OOB read or invalid TWT parameters into a reliable crash, information exposure, or configuration integrity issue.

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

Patch: wifi: mac80211: validate individual TWT params before driver setup [ Upstream
Commit: 92fcd0f30dc8e51f252589b082d46851d295cc1a
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=92fcd0f30dc8e51f252589b082d46851d295cc1a

Changed files:
  net/mac80211/s1g.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=92fcd0f30dc8e51f252589b082d46851d295cc1a

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

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

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

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: 4
  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: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

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