CVE-2026-68195

wifi: mt76: mt7615: drop TXRX_NOTIFY on non-mmio buses

N/A
Published: August 10, 2026 at 12:00 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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").

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.8 ≤ v < 5.10.2655.8 ≤ v < 5.15.2165.8 ≤ v < 6.1.1835.8 ≤ v < 6.12.1015.8 ≤ v < 6.18.425.8 ≤ v < 6.6.1485.8 ≤ v < 7.1.65.8 ≤ v < 7.25.8eb99cc95c3b6513b495c4839ac4917206705f657
Vendor states this is fixed in 1a099d630b8667fa622662b85e35a0ef659fb343 (fixed)
Vendor states this is fixed in 39afc46c0243d10b7795e6e6cf4ae91f41732120 (fixed)
Vendor states this is fixed in 664f8bbc61e45e062679da512bf12f8f6fb26a1b (fixed)
Vendor states this is fixed in 88c98ef247a3126fea9bbbda953a18a2f36c3ea7 (fixed)
Vendor states this is fixed in a0b3e8d8726c3830102a18946c766c94c953c7f2 (fixed)
Vendor states this is fixed in ab4d213393e846baa6437497f94dda7553cbeda7 (fixed)
Vendor states this is fixed in b2ab73b8123ce6cf2bc32634bfee4928676ffa66 (fixed)
Vendor states this is fixed in f2a72f47c5fb4ba6887e85bbe809d7e5b318d9d5 (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.8 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card