CVE-2026-68193 Linux CVE debrief

Who should care

Linux kernel maintainers, Linux distribution vendors, and users of Linux systems with the mt76 driver installed should be aware of this vulnerability. They should assess their exposure, apply patches or updates provided by the Linux kernel maintainers, and monitor for suspicious activity related to TXRX_NOTIFY events. Additionally, they should implement compensating controls, such as filtering or blocking TXRX_NOTIFY events on non-mmio buses, to mitigate the vulnerability until a patch is applied. Linux kernel maintainers should prioritize patching the vulnerability and providing guidance on mitigation strategies. Linux distribution vendors should ensure that their distributions are patched or provide guidance on mitigation strategies for their users. Users of Linux systems with the mt76 driver installed should ensure that their systems are patched and monitor for suspicious activity related to TXRX_NOTIFY events. Security teams should review the vulnerability and implement compensating controls as needed. Operators of Linux systems should assess their exposure and prioritize patching the vulnerability. Vulnerability management teams should track the vulnerability and ensure that affected systems are patched or mitigated. Platform owners should ensure that their platforms are patched or provide guidance on mitigation strategies for their users. Security teams should review the vulnerability and implement compensating controls as needed. Operators of Linux systems should assess their exposure and prioritize patching the vulnerability. Vulnerability management teams should track the vulnerability and ensure that affected systems are patched or mitigated. Platform owners should ensure that their platforms are patched or provide guidance on mitigation strategies for their users. Security teams should review the vulnerability and implement compensating controls as needed. Operators of Linux systems should assess their exposure and prioritize patching the vulnerability. Vulnerability management teams should track the vulnerability and ensure that affected systems are patched or mitigated. Platform owners should ensure that their platforms are patched or provide The 3

Technical summary

The mt7925_mac_tx_free function in the Linux kernel's mt76 driver attempts to clean the DMA tx queues using mt76_queue_tx_cleanup, which calls queue_ops->tx_cleanup. However, the tx_cleanup callback is only implemented for mmio queue ops, and is NULL for USB. When TXRX_NOTIFY is received on a non-mmio bus, this leads to a NULL pointer dereference. The vulnerability was resolved by dropping the TXRX_NOTIFY event on non-mmio buses via mt76_is_mmio. This fix prevents the NULL pointer dereference by ensuring that the tx_cleanup callback is not called on non-mmio buses.

Defensive priority

High

Recommended defensive actions

• Inventory and assess Linux kernel versions using the mt76 driver
• Apply patches or updates provided by the Linux kernel maintainers
• Monitor for suspicious activity related to TXRX_NOTIFY events
• Implement compensating controls, such as filtering or blocking TXRX_NOTIFY events on non-mmio buses
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability was resolved by dropping the TXRX_NOTIFY event on non-mmio buses via mt76_is_mmio. The fix is similar to a previous commit (5683e1488aa9). Evidence is based on official Linux kernel source code changes.

Official resources