# CVE-2026-90370: wifi: mt76: mt7996: bound TLV walk in mt7996_mcu_get_chip_config

> A missing bounds check in the mt7996 WiFi driver allows a malicious firmware response to cause an infinite loop, hanging the CPU during device probe.

- **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:** AZL-102938, BELL-CVE-2026-90370, DEBIAN-CVE-2026-90370, GHSA-mfm7-hr4m-cf88, UBUNTU-CVE-2026-90370

## What is CVE-2026-90370?

CVE-2026-90370 is a denial of service 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: mt7996: bound TLV walk in mt7996_mcu_get_chip_config

The response TLV loop advanced by tlv->len without a minimum, so a
theoretical firmware response containing a zero-length TLV could spin
forever, hanging the CPU during device probe.
The u32 payload was also read without bounds checking.
Reject a short fixed field, stop on a TLV whose length underruns the
header or overruns the skb.

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


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

Apply the vendor's patch.

## Is CVE-2026-90370 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90370 is a denial of service 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-90370 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-90370/ (Markdown: https://insights.sbomify.com/CVE-2026-90370/index.md)
```

## Sources

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

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