Answer in brief
CVE-2026-80937 records a Unknown severity vulnerability in wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e57b7901469fc0b021930b83a8094baaf3d81b09 <5fdaf7016d7684ef756a229fd5d96b4a140eeb40 || >=e57b7901469fc0b021930b83a8094baaf3d81b09 <5f48b0d752a76590e2c613aae5345c2474627d1b || >=e57b7901469fc0b021930b83a8094baaf3d81b09 <44b5adfe49499f53002737f5fe81d608c08122fc | 5fdaf7016d7684ef756a229fd5d96b4a140eeb40, 5f48b0d752a76590e2c613aae5345c2474627d1b, 44b5adfe49499f53002737f5fe81d608c08122fc |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.