Answer in brief
CVE-2026-68195 records a Unknown severity vulnerability in wifi: mt76: mt7615: drop TXRX_NOTIFY on non-mmio buses. 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 | >=eb99cc95c3b6513b495c4839ac4917206705f657 <f2a72f47c5fb4ba6887e85bbe809d7e5b318d9d5 || >=eb99cc95c3b6513b495c4839ac4917206705f657 <88c98ef247a3126fea9bbbda953a18a2f36c3ea7 || >=eb99cc95c3b6513b495c4839ac4917206705f657 <ab4d213393e846baa6437497f94dda7553cbeda7 || >=eb99cc95c3b6513b495c4839ac4917206705f657 <b2ab73b8123ce6cf2bc32634bfee4928676ffa66 || >=eb99cc95c3b6513b495c4839ac4917206705f657 <39afc46c0243d10b7795e6e6cf4ae91f41732120 | f2a72f47c5fb4ba6887e85bbe809d7e5b318d9d5, 88c98ef247a3126fea9bbbda953a18a2f36c3ea7, ab4d213393e846baa6437497f94dda7553cbeda7, b2ab73b8123ce6cf2bc32634bfee4928676ffa66, 39afc46c0243d10b7795e6e6cf4ae91f41732120 |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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").
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68195 records a Unknown severity vulnerability in wifi: mt76: mt7615: drop TXRX_NOTIFY on non-mmio buses. 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 | >=eb99cc95c3b6513b495c4839ac4917206705f657 <f2a72f47c5fb4ba6887e85bbe809d7e5b318d9d5 || >=eb99cc95c3b6513b495c4839ac4917206705f657 <88c98ef247a3126fea9bbbda953a18a2f36c3ea7 || >=eb99cc95c3b6513b495c4839ac4917206705f657 <ab4d213393e846baa6437497f94dda7553cbeda7 || >=eb99cc95c3b6513b495c4839ac4917206705f657 <b2ab73b8123ce6cf2bc32634bfee4928676ffa66 || >=eb99cc95c3b6513b495c4839ac4917206705f657 <39afc46c0243d10b7795e6e6cf4ae91f41732120 | f2a72f47c5fb4ba6887e85bbe809d7e5b318d9d5, 88c98ef247a3126fea9bbbda953a18a2f36c3ea7, ab4d213393e846baa6437497f94dda7553cbeda7, b2ab73b8123ce6cf2bc32634bfee4928676ffa66, 39afc46c0243d10b7795e6e6cf4ae91f41732120 |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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").
Quoted source text, attributed separately from HOL analysis.