Answer in brief
CVE-2025-37944 records a Unknown severity vulnerability in wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.3 | Not reported |
| Linux/Linuxgeneric | >=d889913205cf7ebda905b1e62c5867ed4e39f6c2 <2c512f2eadabb1e80816116894ffaf7d802a944e || >=d889913205cf7ebda905b1e62c5867ed4e39f6c2 <ab7edf42ce800eb34d2f73dd7271b826661a06a5 || >=d889913205cf7ebda905b1e62c5867ed4e39f6c2 <b6a3b2b2cead103089d3bb7a57d8209bdfa5399d || >=d889913205cf7ebda905b1e62c5867ed4e39f6c2 <298f0aea5cb32b5038f991f5db201a0fcbb9a31b || >=d889913205cf7ebda905b1e62c5867ed4e39f6c2 <63fdc4509bcf483e79548de6bc08bf3c8e504bb3 | 2c512f2eadabb1e80816116894ffaf7d802a944e, ab7edf42ce800eb34d2f73dd7271b826661a06a5, b6a3b2b2cead103089d3bb7a57d8209bdfa5399d, 298f0aea5cb32b5038f991f5db201a0fcbb9a31b, 63fdc4509bcf483e79548de6bc08bf3c8e504bb3 |
Published upstream
May 20, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-37944 records a Unknown severity vulnerability in wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.3 | Not reported |
| Linux/Linuxgeneric | >=d889913205cf7ebda905b1e62c5867ed4e39f6c2 <2c512f2eadabb1e80816116894ffaf7d802a944e || >=d889913205cf7ebda905b1e62c5867ed4e39f6c2 <ab7edf42ce800eb34d2f73dd7271b826661a06a5 || >=d889913205cf7ebda905b1e62c5867ed4e39f6c2 <b6a3b2b2cead103089d3bb7a57d8209bdfa5399d || >=d889913205cf7ebda905b1e62c5867ed4e39f6c2 <298f0aea5cb32b5038f991f5db201a0fcbb9a31b || >=d889913205cf7ebda905b1e62c5867ed4e39f6c2 <63fdc4509bcf483e79548de6bc08bf3c8e504bb3 | 2c512f2eadabb1e80816116894ffaf7d802a944e, ab7edf42ce800eb34d2f73dd7271b826661a06a5, b6a3b2b2cead103089d3bb7a57d8209bdfa5399d, 298f0aea5cb32b5038f991f5db201a0fcbb9a31b, 63fdc4509bcf483e79548de6bc08bf3c8e504bb3 |
Published upstream
May 20, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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
Quoted source text, attributed separately from HOL analysis.