wifi: mt76: mt7996: bound the device EEPROM address before the EFUSE copy
CVE-2026-80935 · 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-80935?
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: 98686cd21624c75a043e96812beadddf4f6f48e5 to < 4892be1ef0bbe6db6b13bf46cb79b6706bb5b214, 98686cd21624c75a043e96812beadddf4f6f48e5 to < 388f471ca4758f644394b681ce97677a4d0e772c, 98686cd21624c75a043e96812beadddf4f6f48e5 to < 9e5abb5e2ade0b6fd0e47209711115d47a255176, 98686cd21624c75a043e96812beadddf4f6f48e5 to < 6be59da2063d5b3522bfde8aae0487ec095eb384
- Linux Linux: 6.2
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: mt7996: bound the device EEPROM address before the EFUSE copy
mt7996_mcu_get_eeprom() derives the destination of the EFUSE/EXT block
copy from the address reported by the MCU response (event->addr, a
device-controlled __le32) and clamps only the copy length, never the
destination offset into dev->mt76.eeprom.data. A malicious or
malfunctioning device can report an arbitrary address and drive an
out-of-bounds write of up to MT7996_EXT_EEPROM_BLOCK_SIZE bytes 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/4892be1ef0bbe6db6b13bf46cb79b6706bb5b214
- git.kernel.org/stable/c/388f471ca4758f644394b681ce97677a4d0e772c
- git.kernel.org/stable/c/9e5abb5e2ade0b6fd0e47209711115d47a255176
- git.kernel.org/stable/c/6be59da2063d5b3522bfde8aae0487ec095eb384
- git.kernel.org/stable/c/13b3c29a782033ce4a230be9e5618032813dbcd4
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON