Security readout for executives and security teams
Plain-English summary
This is a Linux kernel crash issue in the ath11k Wi-Fi driver. If spectral scan is enabled and the ath11k module is removed, the system can hit a NULL pointer dereference and crash. The impact is availability, not data theft or privilege escalation based on the provided sources.
Executive priority
Treat as a moderate reliability risk for Linux-based wireless devices, appliances, or embedded platforms. Prioritize patching where ath11k hardware is used and module reloads or diagnostics are common. It is not currently evidenced as internet-exploited or confidentiality-impacting.
Technical view
CVE-2022-49523 is a CWE-476 NULL pointer dereference in Linux ath11k spectral cleanup. During module removal with spectral scan enabled, firmware may still deliver spectral data after the spectral dbring is cleaned, causing an oops in ath11k_spectral_process_data. The fix disables spectral scan via WMI before spectral deinit cleanup.
Likely exposure
Exposure is mainly Linux systems using ath11k-supported Qualcomm WLAN hardware with affected kernel builds and spectral scan enabled. The source lists Linux kernel versions around 5.6 through fixed stable releases, but downstream distro backports may change actual exposure.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, with high availability impact. The provided sources do not show active exploitation, and CISA KEV status is false. Triggering requires local ability to remove ath11k modules while spectral scan is enabled.
Researcher notes
The published fix sequence is narrowly scoped: send spectral scan disable WMI command before cleaning spectral dbring in spectral_deinit. The crash was observed on QCN6122 hw1.0. Affected downstream kernels require vendor-specific confirmation because Linux distributions often backport fixes without changing major versions.
Mitigation direction
Update to a kernel containing the referenced stable ath11k fixes.
Use your Linux distribution or device vendor advisory to confirm backported fixes.
Avoid unloading ath11k modules while spectral scan is enabled until fixed.
If operationally possible, disable spectral scan before ath11k module removal.
Validation and detection
Identify systems using the ath11k driver and Qualcomm WLAN hardware.
Check running kernel versions against vendor-fixed builds or referenced stable commits.
Review kernel logs for ath11k_spectral_process_data NULL pointer oops traces.
Confirm whether spectral scan is enabled in affected operational workflows.
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.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.