* [CVE-2026-99060][MODERATE REGULAR] wifi: mt76: mt7603: initialize global station WCID
@ 2026-10-27 3:15 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-10-27 3:15 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2026-99060
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: wifi: mt76: mt7603: initialize global station WCID
Commit: 99b8bd6323e6fc69615af828522878b7acb77bff
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=99b8bd6323e6fc69615af828522878b7acb77bff
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99060
Analysis date: Mon, 26 Oct 2026 23:15:23 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO
Summary:
Local monitor-interface frame injection can crash an MT7603 system by using an uninitialized global-WCID transmit queue.
======================================================================
ABOUT THIS REPORT
======================================================================
The original Linux kernel CVE announcement for CVE-2026-99060 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99060
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: NO
A detailed explanation of the methodology and priority rules is included
at the end of this message.
======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================
CVE-2026-99060 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-99060 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=MODERATE RESULT=DIFF (final Legacy and Aegis differ; FINAL: MODERATE, Aegis: MODERATE_KPANIC) 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:H';CWE-665;CWE-908;**CWE-476;BEST CVSS score: '5.5';DESCR 'The mt7603 driver publishes its private global station WCID lacking initialization of the embedded transmit queues and list state. Since commit 0335c03, a frame lacking both a station and a vif is queued through this WCID, so the first frame injected through a monitor interface can reach __skb_queue_tail with a NULL prev pointer and cause a kernel oops or system crash. For the CVSS the PR:L value reflects that reliable triggering requires a local process able to configure or use a monitor interface and inject wireless frames. The issue is not demonstrated as remotely reachable through received WiFi traffic. The supported primitive is a NULL pointer dereference rather than UAF, OOB access, or controlled memory corruption, so confidentiality and integrity remain unaffected while availability can be high. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 5.5 and the production ActionableScore returned 1 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE because the CVSS score, vector or bug class threshold rule was applied. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH and V41_INHERITED_KPANIC_PROMOTION_BLOCKED and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 4.4 and ActionableScore 1 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) MAYBE REMOTE INIT RACE NETWORK HARDWARE TEST DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH V41_INHERITED_KPANIC_PROMOTION_BLOCKED MANUAL_REVIEW_REQUIRED - - checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=NO
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO
1. ActionableScore
* Raw base score: 1
* Conservative score: 1
* Raw paranoid score: 1
* Paranoid score: 1
* No floor or cap applied.
* Final recommended bucket: **Ordinary Moderate**::
2. Signal breakdown
* +1 Reliable kernel crash/strong DoS: the first injected stationless/vif-less frame reaches `__skb_queue_tail()` with an uninitialized queue and dereferences a NULL `prev` pointer.
* No privilege penalty: supplied hints support below-host-admin `PR:L` access, but do not establish a specific delegated capability suitable for a `-1` penalty.
* No corruption bonus: the shown operation is a constrained NULL-pointer queue insertion fault, not a useful attacker-directed write.
* No extra availability point: it would duplicate the same oops/crash.
* No UAF, OOB write, controlled reclaim, disclosure, integrity impact, or remote reachability is shown.
* B5-R does not apply: there is no retry-accumulated heap OOB write or later consumption of corrupted heap state.
* B3-PENDING and B4-PENDING do not apply: neither shared-backing modification nor an authorization decision bypass exists.
3. Reachability analysis
The grounded trigger is local frame injection through an MT7603 monitor interface. The hints classify this as low privilege, supporting `HostAdminRequired=NO`, but the evidence does not identify whether an ordinary user, delegated wireless service, namespace capability, or preconfigured interface supplies access. Therefore namespace-scoped privilege and numeric UID requirements remain unknown. No received-WiFi remote path is shown. MT7603 PCIe hardware and monitor injection are required, but the hardware is not proven sufficiently rare for a penalty. No timing race is required.
4. Primitive and severity reading
The defect publishes an active WCID without initializing its embedded queues and list state. Its first queue insertion follows a NULL link and faults. This is invalid-state/NULL-dereference behavior, classified as CLASS_C rather than UAF or exploitable heap corruption. The supported effect is kernel oops or crash; arbitrary write, useful state corruption, and privilege escalation are unproven. Thus it is not an Important candidate and may be downgraded after review.
5. One-sentence report phrase
Local monitor-interface frame injection can crash an MT7603 system by using an uninitialized global-WCID transmit queue.
6. Manual review advice
MANUAL CHECK RECOMMENDED
Confirm actual monitor-interface creation and injection permissions in the affected product.
7. Call-site confidence
Call-site confidence: high
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: wifi: mt76: mt7603: initialize global station WCID
Commit: 99b8bd6323e6fc69615af828522878b7acb77bff
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=99b8bd6323e6fc69615af828522878b7acb77bff
Commit description:
mt7603 uses a driver-private global station WCID for frames that have
neither a station nor a vif, including frames injected through a monitor
interface. Unlike the core global WCID initialized by
mt76_register_device(), this WCID is published without ever being passed
to mt76_wcid_init().
Since commit 0335c03 ("wifi: mt76: fix race condition related to
checking tx queue fill status"), mt76_tx() queues every such frame on the
WCID's tx_pending or tx_offchannel queue and links its tx_list. The first
injected frame therefore reaches __skb_queue_tail() with an uninitialized
sk_buff_head and dereferences a NULL prev pointer.
Initialize the WCID before publishing it.
The fix was tested on an MT7603 PCIe device. Three wildcard probe requests
were injected through a monitor interface. The hardware queue head and tail
advanced from 0 to 3 and a second radio captured the third request over the
air. No oops or reset occurred. After restoring AP mode, a 150 MB transfer
also completed without a reset.
Fixes: 0335c03 ("wifi: mt76: fix race condition related to checking tx queue fill status")
Cc: [email protected]
Signed-off-by: Cristian Papa <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Felix Fietkau <[email protected]>
[ mt76_wcid_init() takes no band index in this tree; drop the argument. ]
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Cristian Papa <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
Changed files:
drivers/net/wireless/mediatek/mt76/mt7603/init.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=99b8bd6323e6fc69615af828522878b7acb77bff
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2026-99060 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99060
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: Not available
The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
The Best / paranoid CVSS score: 5.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: unknown
Paranoid ActionableScore: 1
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 [email protected] (and both
send reply to CVE record itself too and see "reply" button below for howto reply).
^ permalink raw reply [relevance 21%]
Results 1-1 of 1 | reverse | sort options + mbox downloads above
-- links below jump to the message on this page --
2026-10-27 3:15 21% [CVE-2026-99060][MODERATE REGULAR] wifi: mt76: mt7603: initialize global station WCID AL-KERNEL
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox