Linux
wifi: ath11k: cancel SSR work items during PCI shutdown
In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: cancel SSR work items during PCI shutdown A reboot can crash the kernel if it overlaps with WLAN firmware crash recovery (SSR). The crash is a NULL pointer dereference in the MHI teardown path while freeing DMA-backed MHI contexts. Simplified trace: dma_free_attrs mhi_deinit_dev_ctxt [mhi] ath11k_pci_power_down [ath11k_pci] ath11k_pci_shutdown [ath11k_pci] device_shutdown kernel_restart On the host side, SSR is driven by the MHI RDDM callback, which queues reset_work to perform device recovery. reset_work power-cycles the device by calling ath11k_hif_power_down() followed by ath11k_hif_power_up(). The power-down phase deinitializes MHI and frees DMA resources. Shutdown/reboot runs fully asynchronously with this RDDM-driven SSR recovery flow. As a result, the shutdown path (ath11k_pci_shutdown() -> ath11k_pci_power_down()) can race with the SSR recovery sequence. Fix this by canceling SSR-related work items during PCI shutdown, marking the device as unregistering, and serializing the RDDM callback path that checks and queues reset_work. This ensures that no new SSR recovery work can be queued once teardown has started, and that any in-flight recovery work is fully synchronized before device power-down, preventing MHI teardown and DMA resource freeing from running more than once. Note: This issue only affects PCI/MHI-based devices. AHB-based ath11k devices do not queue reset_work in normal SSR flows. Tested-on: WCN6855 hw2.1 PCI WLAN.HSP.1.1-04866.5-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 13da397f884d9c9a3fb6616206eeb6c6ab097287, < 7630eb217166435e8a6dd501fa4ad304e2264407
- >= 13da397f884d9c9a3fb6616206eeb6c6ab097287, < f82d42577ee4a191b0ad0f0a3b49fc1935dff845
- >= 13da397f884d9c9a3fb6616206eeb6c6ab097287, < daeb44fb8d700654f37f54d1ee36cd67645d0d34
- >= 13da397f884d9c9a3fb6616206eeb6c6ab097287, < 6dd3701facc0cee62d6682e49eed64499f9d0e43
- >= 13da397f884d9c9a3fb6616206eeb6c6ab097287, < 53dd29e8aeb2a1b5f079178551836b85fc6b53df
- >= 13da397f884d9c9a3fb6616206eeb6c6ab097287, < 8c79aac429b583301f387374ff37c59be671df87
Fixed in 7630eb217166435e8a6dd501fa4ad304e2264407, f82d42577ee4a191b0ad0f0a3b49fc1935dff845, daeb44fb8d700654f37f54d1ee36cd67645d0d34, 6dd3701facc0cee62d6682e49eed64499f9d0e43, 53dd29e8aeb2a1b5f079178551836b85fc6b53df, 8c79aac429b583301f387374ff37c59be671df87
- 5.19
Fixed in 0, 6.1.191, 6.6.160, 6.12.114, 6.18.53, 7.1.5, 7.2
Mitigation
Upgrade Linux to 7630eb217166435e8a6dd501fa4ad304e2264407 or f82d42577ee4a191b0ad0f0a3b49fc1935dff845 or daeb44fb8d700654f37f54d1ee36cd67645d0d34 or 6dd3701facc0cee62d6682e49eed64499f9d0e43 or 53dd29e8aeb2a1b5f079178551836b85fc6b53df or 8c79aac429b583301f387374ff37c59be671df87 or later.
Upgrade Linux to 0 or 6.1.191 or 6.6.160 or 6.12.114 or 6.18.53 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.