| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-37743: wifi: ath12k: Avoid memory leak while enabling statistics |
| |
| 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 |
| |
| The Linux kernel CVE team has assigned CVE-2025-37743 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.3 with commit d889913205cf7ebda905b1e62c5867ed4e39f6c2 and fixed in 6.14.3 with commit 286bab0fc7b9db728dab8c63cadf6be9b3facf8c |
| Issue introduced in 6.3 with commit d889913205cf7ebda905b1e62c5867ed4e39f6c2 and fixed in 6.15 with commit ecfc131389923405be8e7a6f4408fd9321e4d19b |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2025-37743 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/net/wireless/ath/ath12k/dp_mon.c |
| drivers/net/wireless/ath/ath12k/hal_rx.h |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/286bab0fc7b9db728dab8c63cadf6be9b3facf8c |
| https://git.kernel.org/stable/c/ecfc131389923405be8e7a6f4408fd9321e4d19b |
