CVE-2025-37944: wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process
Currently, ath12k_dp_mon_srng_process uses ath12k_hal_srng_src_get_next_entry
to fetch the next entry from the destination ring. This is incorrect because
ath12k_hal_srng_src_get_next_entry is intended for source rings, not destination
rings. This leads to invalid entry fetches, causing potential data corruption or
crashes due to accessing incorrect memory locations. This happens because the
source ring and destination ring have different handling mechanisms and using
the wrong function results in incorrect pointer arithmetic and ring management.
To fix this issue, replace the call to ath12k_hal_srng_src_get_next_entry with
ath12k_hal_srng_dst_get_next_entry in ath12k_dp_mon_srng_process. This ensures
that the correct function is used for fetching entries from the destination
ring, preventing invalid memory accesses.
Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1
Tested-on: WCN7850 hw2.0 WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
Security readout for executives and security teams
Plain-English summary
A Linux ath12k Wi-Fi driver defect can fetch the wrong ring entry, potentially accessing incorrect memory and causing data corruption or crashes. The supplied CVSS score is 8.8, reflecting serious confidentiality, integrity, and availability consequences from an adjacent network position without credentials or user interaction.
Executive priority
Treat this as a high-priority kernel maintenance issue for ath12k-equipped systems, especially those operating near untrusted wireless devices. Accelerate supported kernel updates, but avoid declaring an emergency based on exploitation: the supplied evidence shows serious potential impact without confirming attacks in the wild.
Technical view
ath12k_dp_mon_srng_process incorrectly calls the source-ring accessor for a destination ring. Different pointer arithmetic and ring-management rules can produce invalid entries and memory accesses. The stable-kernel fix substitutes ath12k_hal_srng_dst_get_next_entry. The source bundle reports testing on QCN9274 and WCN7850 hardware.
Likely exposure
Exposure centers on Linux systems actively using the ath12k wireless driver. QCN9274 and WCN7850 were tested, but the sources do not establish that exposure is limited to them. The supplied affected-version list is ambiguous, so determine exposure through distribution advisories and fix-commit inclusion rather than version strings alone.
Exploitation context
The CVSS vector describes adjacent-network reachability, low complexity, no privileges, and no user interaction. However, the bundle provides no exploit demonstration, technical trigger details, or evidence of attacks. CISA KEV status is false, so active exploitation should not be claimed.
Researcher notes
The defect is an accessor mismatch between source and destination rings, corrected by a one-call substitution. Invalid pointer arithmetic may explain corruption or crashes, but the bundle does not establish exploitability beyond its CVSS assessment. Exact vulnerable branches should be mapped using the five stable commits and distribution backport records.
Mitigation direction
Install a vendor-supported kernel update containing the referenced stable fix.
Check Linux distribution advisories for the corrected package version.
Prioritize systems using ath12k Wi-Fi in untrusted or shared wireless environments.
If updating is delayed, consult the vendor for supported exposure-reduction measures.
Validation and detection
Inventory Linux hosts, kernel builds, wireless chipsets, and ath12k driver usage.
Confirm the installed kernel contains the applicable referenced stable fix commit.
Review kernel logs and monitoring for ath12k crashes or unexplained memory corruption.
Retest wireless monitoring and normal connectivity after updating.
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-37944 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
0ADP providers
6Source 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.