wifi: mt76: mt7615: drop TXRX_NOTIFY on non-mmio buses
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ eb99cc95c3b6513b495c4839ac4917206705f657 · < ab4d213393e846baa6437497f94dda7553cbeda7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7615: drop TXRX_NOTIFY on non-mmio buses
PKT_TYPE_TXRX_NOTIFY is an mmio-only event, but mt7615_rx_check() and mt7615_queue_rx_skb() dispatch it to mt7615_mac_tx_free() on every bus. mt7615_mac_tx_free() cleans the DMA tx queues with mt76_queue_tx_cleanup(), which calls queue_ops->tx_cleanup(). Only the mmio queue ops implement that callback; on the mt7663 USB and SDIO buses it is NULL, so a TXRX_NOTIFY there calls a NULL pointer in the RX worker. Same defect as the mt7921 and mt7925 patches in this series.
Drop the event on non-mmio buses via mt76_is_mmio(), as in commit 5683e1488aa9 ("wifi: mt76: connac: do not check WED status for non-mmio devices").
From the CVE record · Linux
The Linux kernel's mt7615 Wi-Fi driver processes an MMIO-only TXRX_NOTIFY event on non-MMIO buses. On mt7663 USB and SDIO devices, that event can trigger a NULL-pointer call in the receive worker. The input does not specify an attacker path or authentication requirements.
Operators running the Linux kernel with mt7663 USB or SDIO Wi-Fi devices should check their kernel version; affected versions are not specified.