# CVE-2026-80937: wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy

> A malicious WiFi device can trigger an out-of-bounds write in the mt7915 driver, potentially allowing code execution or privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-100416, BELL-CVE-2026-80937, DEBIAN-CVE-2026-80937, GHSA-c9p9-v2fp-rr7g, UBUNTU-CVE-2026-80937

## What is CVE-2026-80937?

CVE-2026-80937 is a high-severity memory corruption vulnerability in Linux, published on 11 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: mt7915: bound the device EEPROM address before the EFUSE copy

mt7915_mcu_get_eeprom() copies a fixed EFUSE block into the driver's
dev->mt76.eeprom.data buffer at the offset reported by the MCU response
(res->addr, a device-controlled __le32) without checking it against the
buffer size. A malicious or malfunctioning device can report an arbitrary
address and drive a 16-byte out-of-bounds write past eeprom.data.

Reject a response whose address would place the copy outside eeprom.data
before deriving the destination pointer. Devices that echo the requested
in-bounds offset are unaffected.

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


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

Apply the vendor's patch.

## Is CVE-2026-80937 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80937 is a high-severity memory corruption vulnerability in Linux, published on 11 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-80937 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-80937/ (Markdown: https://insights.sbomify.com/CVE-2026-80937/index.md)
```

## Sources

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

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