CVE-2026-80935: Linux kernel · wifi: mt76: mt7996: bound the device EEPROM address before the EFUSE copy
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in 4892be1ef0bbe6db6b13bf46cb79b6706bb5b214 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:30 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4892be1ef0bbe6db6b13bf46cb79b6706bb5b214, 388f471ca4758f644394b681ce97677a4d0e772c, 13b3c29a782033ce4a230be9e5618032813dbcd4 +2
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/4892be1ef0bbe6db6b13bf46cb79b6706bb5b214 (opens in a new tab)
- git.kernel.org/stable/c/388f471ca4758f644394b681ce97677a4d0e772c (opens in a new tab)
- git.kernel.org/stable/c/9e5abb5e2ade0b6fd0e47209711115d47a255176 (opens in a new tab)
- git.kernel.org/stable/c/6be59da2063d5b3522bfde8aae0487ec095eb384 (opens in a new tab)
- git.kernel.org/stable/c/13b3c29a782033ce4a230be9e5618032813dbcd4 (opens in a new tab)