# CVE-2026-99060: wifi: mt76: mt7603: initialize global station WCID


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** BELL-CVE-2026-99060, DEBIAN-CVE-2026-99060, GHSA-88mv-32mf-f27j, UBUNTU-CVE-2026-99060

## What is CVE-2026-99060?

CVE-2026-99060 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

wifi: mt76: mt7603: initialize global station WCID

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 0335c034e726 ("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.

## Which versions are affected by CVE-2026-99060?


## How do I fix CVE-2026-99060?

Upgrade to a fixed version.

## Is CVE-2026-99060 being exploited?

There is no known exploitation of CVE-2026-99060 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99060 and fix it if it is affected.

What it is: CVE-2026-99060 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99060 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99060/ (Markdown: https://insights.sbomify.com/CVE-2026-99060/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99060
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99060
- OSV: https://osv.dev/vulnerability/CVE-2026-99060

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99060/
Summaries are generated and may contain mistakes; the official description above is the record.