CVE-2026-99560 in Linux
Summary
by MITRE • 11/19/2026
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7925: fix reset panic caused by the WM2 rx irq mask
mt7925_irq_map sets wm2_complete_mask, but mt7925_dma_layout has no tx done ring, so the MT_RXQ_MCU_WA queue and its NAPI are never set up. On a chip reset, mt7925e_mac_reset() calls napi_disable() on that NAPI and crashes:
BUG: kernel NULL pointer dereference, address: 0000000000000a40 Workqueue: mt76 mt7925_mac_reset_work [mt7925_common]
RIP: 0010:mutex_lock+0x1c/0x50 Call Trace: napi_disable+0x1d/0x50 mt7925e_mac_reset+0x327/0x420 [mt7925e]
mt7925_mac_reset_work+0x9a/0x1a0 [mt7925_common]
Remove the WM2 mask from mt7925_irq_map and from MT7925_INT_RX_DONE_ALL.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/22/2026
The vulnerability identified in the Linux kernel involves a critical NULL pointer dereference within the MediaTek mt7925 Wi-Fi driver, specifically triggered during hardware reset operations. This issue stems from an inconsistency between interrupt mapping configurations and DMA layout definitions for the WM2 (Wi-Fi Module 2) subsystem. When the system undergoes a chip reset, the function mt7925e_mac_reset is invoked to reinitialize the MAC layer. As part of this process, it attempts to disable network interfaces associated with specific queues by calling napi_disable on NAPI structures linked to those queues. However, due to a misconfiguration in how interrupt masks are mapped relative to available DMA rings, the driver references a NAPI structure that was never properly initialized or allocated, leading directly to a kernel panic and system instability.
The root cause lies in the interaction between mt7925_irq_map and mt7925_dma_layout functions within the driver codebase. The mt7925_irq_map function incorrectly sets up the wm2_complete_mask, implying that there is an associated transmit completion ring for WM2. In reality, the mt7925_dma_layout configuration indicates that no such tx done ring exists for this specific module. Consequently, the MT_RXQ_MCU_WA queue and its corresponding NAPI context are never set up during initialization. When a reset occurs, the driver blindly attempts to access resources tied to this non-existent setup. The call trace reveals that napi_disable triggers a mutex lock operation on a NULL pointer address 0x000000000000a40, resulting in an immediate kernel crash as reported by the BUG: kernel NULL pointer dereference message.
From a security and operational impact perspective, this vulnerability allows for local denial of service conditions if an attacker can trigger hardware resets or cause driver instability through network traffic patterns that induce reset cycles. While primarily affecting system stability rather than allowing direct privilege escalation or remote code execution in most standard configurations, the resulting kernel panic disrupts all services running on the affected host. This aligns with CWE-476, which describes a NULL pointer dereference vulnerability where software fails to check for null pointers before using them, leading to crashes or unexpected behavior. The attack vector typically involves manipulating network conditions that force the wireless driver into error states requiring reset procedures, thereby exploiting the lack of defensive checks against uninitialized NAPI structures during critical lifecycle events like hardware resets.
Mitigation strategies involve applying the upstream kernel patch that corrects the interrupt mapping logic by removing the WM2 mask from mt7925_irq_map and excluding it from MT7925_INT_RX_DONE_ALL definitions. This ensures that the driver does not attempt to manage resources for queues that do not exist in the current hardware configuration. Administrators should ensure their systems are updated with the latest stable kernel versions containing this fix. Additionally, monitoring system logs for mt76 or mt7925 related errors can help identify instances where the driver might be encountering similar initialization issues before a full reset occurs. For environments requiring high availability, implementing watchdog mechanisms that detect and recover from such panics may provide temporary resilience until patches are deployed. The fix aligns with best practices in defensive programming by ensuring resource allocation matches actual hardware capabilities as defined in DMA layouts, preventing future inconsistencies between interrupt handling and data path configurations.