cveboard RSS feed

CVE-2026-74407

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

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

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
13da397f884d9c9a3fb6616206eeb6c6ab097287affectedgitf82d42577ee4a191b0ad0f0a3b49fc1935dff845UnavailableNone listed
13da397f884d9c9a3fb6616206eeb6c6ab097287affectedgitdaeb44fb8d700654f37f54d1ee36cd67645d0d34UnavailableNone listed
13da397f884d9c9a3fb6616206eeb6c6ab097287affectedgit6dd3701facc0cee62d6682e49eed64499f9d0e43UnavailableNone listed
13da397f884d9c9a3fb6616206eeb6c6ab097287affectedgit53dd29e8aeb2a1b5f079178551836b85fc6b53dfUnavailableNone listed
13da397f884d9c9a3fb6616206eeb6c6ab097287affectedgit8c79aac429b583301f387374ff37c59be671df87UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
5.19affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver5.19UnavailableNone listed
6.6.160unaffectedsemverUnavailable6.6.*None listed
6.12.114unaffectedsemverUnavailable6.12.*None listed
6.18.53unaffectedsemverUnavailable6.18.*None listed
7.1.5unaffectedsemverUnavailable7.1.*None listed
7.2unaffectedoriginal_commit_for_fixUnavailable*None listed