wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy
CVE-2026-80937 · published 11 Sept 2026
How serious is it
- Severity: high, CVSS score 8.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-80937?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: e57b7901469fc0b021930b83a8094baaf3d81b09 to < d6774f6af3711143a93281904a928a78652c8b7e, e57b7901469fc0b021930b83a8094baaf3d81b09 to < 394e8cb56fc732d71041599cdb4e01f82cfd11c5, e57b7901469fc0b021930b83a8094baaf3d81b09 to < 5fdaf7016d7684ef756a229fd5d96b4a140eeb40, e57b7901469fc0b021930b83a8094baaf3d81b09 to < 5f48b0d752a76590e2c613aae5345c2474627d1b
- Linux Linux: 5.8
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/d6774f6af3711143a93281904a928a78652c8b7e
- git.kernel.org/stable/c/394e8cb56fc732d71041599cdb4e01f82cfd11c5
- git.kernel.org/stable/c/5fdaf7016d7684ef756a229fd5d96b4a140eeb40
- git.kernel.org/stable/c/5f48b0d752a76590e2c613aae5345c2474627d1b
- git.kernel.org/stable/c/44b5adfe49499f53002737f5fe81d608c08122fc
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON