CVE-2023-52827: wifi: ath12k: fix possible out-of-bound read in ath12k_htt_pull_ppdu_stats()
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath12k: fix possible out-of-bound read in ath12k_htt_pull_ppdu_stats()
len is extracted from HTT message and could be an unexpected value in
case errors happen, so add validation before using to avoid possible
out-of-bound read in the following message iteration and parsing.
The same issue also applies to ppdu_info->ppdu_stats.common.num_users,
so validate it before using too.
These are found during code review.
Compile test only.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a possible out-of-bounds read in the ath12k Wi-Fi driver. It was found by code review, not reported as exploited. Business risk depends on whether affected systems use ath12k-supported wireless hardware and kernels mapped to the vulnerable range.
Executive priority
Treat as a targeted kernel maintenance item, not an emergency, unless your fleet depends on affected ath12k Wi-Fi systems. Patch through normal kernel update channels and verify vendor backports.
Technical view
The flaw is in ath12k_htt_pull_ppdu_stats(), where a length value from an HTT message and num_users could be unexpected. The fix adds validation before iterating and parsing PPDU statistics to avoid out-of-bounds reads. The source states compile testing only.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel builds with the ath12k Wi-Fi driver relevant to supported Qualcomm wireless hardware. The source lists Linux kernel versions including 6.3, 6.5.13, 6.6.3, and 6.7, but distro backport status must be verified.
Exploitation context
The source says the issue was found during code review and compile-tested only. No KEV entry, public exploitation, exploit method, or attacker prerequisites are provided in the supplied sources.
Researcher notes
Impact details are incomplete: no CVSS, CWE, exploitability analysis, or runtime test evidence is provided. The key evidence is the kernel fix rationale: validating HTT-provided length and user count before PPDU stats parsing.
Mitigation direction
Apply a vendor kernel update that includes the referenced ath12k validation fixes.
Check Linux distribution advisories for backported fixes to your supported kernel packages.
Prioritize systems with ath12k wireless hardware or enabled ath12k kernel modules.
Follow vendor guidance if no package update is currently available.
Validation and detection
Inventory Linux kernel versions and map them to vendor advisory status.
Identify systems with ath12k driver support enabled or loaded.
Confirm kernel packages include one of the referenced stable fixes or equivalent backport.
Record unsupported or unclear kernels for vendor follow-up.
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-2023-52827 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.