# CVE-2026-90350: wifi: mt76: reject out-of-range link ids in mt76_vif_link()

> An out-of-bounds read in the mt76 WiFi driver allows attackers to access adjacent memory or cause a crash via crafted link IDs.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-90350, DEBIAN-CVE-2026-90350, GHSA-2wwg-wpch-pp6g, UBUNTU-CVE-2026-90350

## What is CVE-2026-90350?

CVE-2026-90350 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

wifi: mt76: reject out-of-range link ids in mt76_vif_link()

mt76_vif_link() indexes mvif->link[] without validating link_id, but
callers pass mvif->deflink_id / msta->deflink_id, which hold
IEEE80211_LINK_UNSPECIFIED (0xf) until the first link has been added.
Since IEEE80211_MLD_MAX_NUM_LINKS is 15, that reads one element past the
end of the array, aliasing mt76_vif_data.offchannel_link.

Reachable via mt7996_set_tsf()/mt7996_offset_tsf() and
mt7996_net_fill_forward_path(). Bounds check link_id and return NULL,
matching mt7996_sta_link() and mt7996_sta_link_protected().

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


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

Apply the vendor's patch.

## Is CVE-2026-90350 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90350 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90350 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-90350/ (Markdown: https://insights.sbomify.com/CVE-2026-90350/index.md)
```

## Sources

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

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