[CVE-2026-68306][MODERATE REGULAR] wifi: mt76: mt7996: fix possible NULL-pointer deref in mt7996_mcu_sta_bfer_eht() [ Upstream

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

CVE: CVE-2026-68306
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: wifi: mt76: mt7996: fix possible NULL-pointer deref in mt7996_mcu_sta_bfer_eht() [ Upstream
Commit: 2b1882cf313ae44181146629b3578a7826c672c9
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2b1882cf313ae44181146629b3578a7826c672c9
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68306
Analysis date: Mon, 10 Aug 2026 19:26:52 -0400
ActionableScore: 4
ActionableScore lower bound: 3
Actionable bucket: Borderline manual review recommended / ordinary Moderate with adjacent-network exposure
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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 REGULAR
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-68306	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:N/I:N/A:H';**CWE-476;CWE-252;CWE-703;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '6.5';DESCR 'A NULL pointer dereference in the mt7996 EHT beamforming setup path can occur because mt7996_mcu_sta_bfer_eht() dereferenced the result of mt76_connac_get_eht_phy_cap() without checking whether it returned NULL. An adjacent wireless peer may be able to reach this code during station capability handling or association related configuration on affected mt7996 deployments with EHT beamforming support. For the CVSS the PR:N is used because the paranoid interpretation assumes no local shell access is needed beyond adjacent WiFi reachability to the affected access point or peer handling path. The issue is not Internet reachable and requires proximity or access to the relevant wireless network. Impact is denial of service via kernel crash only. There is no supported UAF, OOB write, information leak, or privilege escalation primitive in the provided patch context.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended / ordinary Moderate with adjacent-network exposure (with actual score 4)  SKIP CVE-2026-68306 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE SIMPLEFIX NETWORK  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

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

ActionableScore=4
ActionableScoreLower=3

1. ActionableScore
* Conservative score: 3
* Paranoid score: 4
* Final recommended bucket: **Borderline manual review recommended / ordinary Moderate with adjacent-network exposure**::

2. Signal breakdown
* Remote reachable / network-triggerable: +2. The plausible trigger is adjacent wireless reachability during STA capability handling or association-related EHT beamforming setup, not Internet reachability.
* Reliable kernel crash / strong DoS: +1. The bug is a NULL pointer dereference in kernel driver code if `mt76_connac_get_eht_phy_cap()` returns NULL.
* Availability impact realistic: +1 only in the paranoid score. A kernel NULL dereference can cause Oops or panic depending on context and system policy, but the patch does not show persistent corruption.
* No memory corruption bonus. The patch supports NULL dereference only, not UAF, double free, OOB write, object reuse, callback control, or refcount abuse.
* No LPE bonus. There is no supported privilege escalation primitive.
* No C/I impact. No information leak or integrity primitive is shown.

3. Reachability analysis
An adjacent WiFi peer may be able to reach the affected path if the device uses mt7996 with EHT beamforming support and the relevant STA/VIF capability state causes `mt76_connac_get_eht_phy_cap()` to return NULL. No local account is required under the paranoid interpretation, but physical proximity or access to the affected wireless network is required. This is device and configuration dependent, but it is not merely a local admin control-plane bug. Call-site confidence: medium, because the changed function is visible but the full association/capability call chain is not included.

4. Severity interpretation
This behaves like an ordinary to borderline Moderate adjacent-network DoS. The theoretical impact is kernel crash only. Realistic exploitation evidence for memory corruption, confidentiality impact, integrity impact, or privilege escalation is absent. The issue should not be treated as Important unless additional evidence shows that an attacker-controlled wireless peer can reliably trigger the NULL return in common deployments.

5. One-sentence report phrase
A NULL pointer dereference in the mt7996 EHT beamforming setup path may allow an adjacent wireless peer to crash an affected kernel during station capability handling, with no evidence of privilege escalation or data exposure.

6. Manual review recommendation
MANUAL CHECK RECOMMENDED.
Manual review is recommended because the bug is adjacent-network reachable on affected WiFi hardware, but the supported impact is DoS-only and the patch does not indicate memory corruption beyond a NULL dereference.

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

Patch: wifi: mt76: mt7996: fix possible NULL-pointer deref in mt7996_mcu_sta_bfer_eht() [ Upstream
Commit: 2b1882cf313ae44181146629b3578a7826c672c9
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2b1882cf313ae44181146629b3578a7826c672c9

Changed files:
  drivers/net/wireless/mediatek/mt76/mt7996/mcu.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=2b1882cf313ae44181146629b3578a7826c672c9

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

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

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

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: 3
  Paranoid ActionableScore: 4

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

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