CVE-2025-38293: wifi: ath11k: fix node corruption in ar->arvifs list
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath11k: fix node corruption in ar->arvifs list
In current WLAN recovery code flow, ath11k_core_halt() only
reinitializes the "arvifs" list head. This will cause the
list node immediately following the list head to become an
invalid list node. Because the prev of that node still points
to the list head "arvifs", but the next of the list head "arvifs"
no longer points to that list node.
When a WLAN recovery occurs during the execution of a vif
removal, and it happens before the spin_lock_bh(&ar->data_lock)
in ath11k_mac_op_remove_interface(), list_del() will detect the
previously mentioned situation, thereby triggering a kernel panic.
The fix is to remove and reinitialize all vif list nodes from the
list head "arvifs" during WLAN halt. The reinitialization is to make
the list nodes valid, ensuring that the list_del() in
ath11k_mac_op_remove_interface() can execute normally.
Call trace:
__list_del_entry_valid_or_report+0xb8/0xd0
ath11k_mac_op_remove_interface+0xb0/0x27c [ath11k]
drv_remove_interface+0x48/0x194 [mac80211]
ieee80211_do_stop+0x6e0/0x844 [mac80211]
ieee80211_stop+0x44/0x17c [mac80211]
__dev_close_many+0xac/0x150
__dev_change_flags+0x194/0x234
dev_change_flags+0x24/0x6c
devinet_ioctl+0x3a0/0x670
inet_ioctl+0x200/0x248
sock_do_ioctl+0x60/0x118
sock_ioctl+0x274/0x35c
__arm64_sys_ioctl+0xac/0xf0
invoke_syscall+0x48/0x114
...
Tested-on: QCA6698AQ hw2.1 PCI WLAN.HSP.1.1-04591-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux ath11k Wi-Fi driver can corrupt an internal interface list when wireless recovery overlaps interface removal. The resulting consistency check can panic the kernel, abruptly disrupting the affected device or service. The supplied evidence demonstrates a crash condition, but does not establish practical confidentiality or integrity impact despite the 8.8 CVSS score.
Executive priority
Treat this as a high-priority availability issue for ath11k-equipped Linux endpoints, appliances, and operational systems. Patch promptly where crashes would interrupt critical service. Broader emergency action is not supported because the bundle provides no evidence of active exploitation and does not establish impact beyond kernel panic.
Technical view
During ath11k WLAN recovery, ath11k_core_halt() reinitializes only the ar->arvifs list head, leaving adjacent nodes inconsistent. If interface removal reaches list_del() after this recovery state is created, kernel list validation can trigger a panic. The upstream fix removes and reinitializes every virtual-interface node during halt.
Likely exposure
Exposure is limited to Linux systems using the ath11k driver and vulnerable kernel code, with the triggering race requiring WLAN recovery during virtual-interface removal. The source lists several affected kernel versions, but its version formatting is ambiguous. The reported test platform was QCA6698AQ hw2.1; applicability to other ath11k hardware is not established here.
Exploitation context
The supplied record does not report active exploitation, and it is not marked as CISA KEV. No public exploit evidence is included. Triggering requires an adjacent WLAN condition and a specific timing overlap, so real-world exploitability cannot be determined from this bundle alone.
Researcher notes
The documented root cause is stale bidirectional-list linkage following partial list reinitialization. The failure is a race between WLAN recovery and ath11k_mac_op_remove_interface(). Stable-kernel commits are supplied for multiple branches. Researchers should avoid generalizing beyond ath11k or the tested QCA6698AQ platform without additional evidence.
Mitigation direction
Install a vendor-supported kernel containing the applicable upstream ath11k correction.
Review Linux distribution advisories to identify the corrected package for each deployed kernel.
Prioritize Wi-Fi-dependent systems where an unexpected kernel panic would materially disrupt operations.
If immediate patching is unavailable, consult vendor guidance for supported temporary mitigations.
Validation and detection
Inventory systems loading ath11k and identify their exact kernel builds and wireless hardware.
Compare deployed kernel packages with vendor advisories and the referenced stable-kernel fixes.
Review kernel logs for ath11k recovery, list corruption, or the documented remove-interface panic trace.
After updating, confirm the running kernel package includes the applicable backported correction.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38293 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
10Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.