| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-47724: wifi: ath11k: use work queue to process beacon tx event |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| wifi: ath11k: use work queue to process beacon tx event |
| |
| Commit 3a415daa3e8b ("wifi: ath11k: add P2P IE in beacon template") |
| from Feb 28, 2024 (linux-next), leads to the following Smatch static |
| checker warning: |
| |
| drivers/net/wireless/ath/ath11k/wmi.c:1742 ath11k_wmi_p2p_go_bcn_ie() |
| warn: sleeping in atomic context |
| |
| The reason is that ath11k_bcn_tx_status_event() will directly call might |
| sleep function ath11k_wmi_cmd_send() during RCU read-side critical |
| sections. The call trace is like: |
| |
| ath11k_bcn_tx_status_event() |
| -> rcu_read_lock() |
| -> ath11k_mac_bcn_tx_event() |
| -> ath11k_mac_setup_bcn_tmpl() |
| …… |
| -> ath11k_wmi_bcn_tmpl() |
| -> ath11k_wmi_cmd_send() |
| -> rcu_read_unlock() |
| |
| Commit 886433a98425 ("ath11k: add support for BSS color change") added the |
| ath11k_mac_bcn_tx_event(), commit 01e782c89108 ("ath11k: fix warning |
| of RCU usage for ath11k_mac_get_arvif_by_vdev_id()") added the RCU lock |
| to avoid warning but also introduced this BUG. |
| |
| Use work queue to avoid directly calling ath11k_mac_bcn_tx_event() |
| during RCU critical sections. No need to worry about the deletion of vif |
| because cancel_work_sync() will drop the work if it doesn't start or |
| block vif deletion until the running work is done. |
| |
| Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 |
| |
| The Linux kernel CVE team has assigned CVE-2024-47724 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.10 with commit 3a415daa3e8ba65f1cc976c172a5ab69bdc17e69 and fixed in 6.10.13 with commit dbd51da69dda1137723b8f66460bf99a9dac8dd2 |
| Issue introduced in 6.10 with commit 3a415daa3e8ba65f1cc976c172a5ab69bdc17e69 and fixed in 6.11.2 with commit 6db232905e094e64abff1f18249905d068285e09 |
| Issue introduced in 6.10 with commit 3a415daa3e8ba65f1cc976c172a5ab69bdc17e69 and fixed in 6.12 with commit 177b49dbf9c1d8f9f25a22ffafa416fc2c8aa6a3 |
| |
| 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-2024-47724 |
| 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/ath11k/core.h |
| drivers/net/wireless/ath/ath11k/mac.c |
| drivers/net/wireless/ath/ath11k/wmi.c |
| |
| |
| 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/dbd51da69dda1137723b8f66460bf99a9dac8dd2 |
| https://git.kernel.org/stable/c/6db232905e094e64abff1f18249905d068285e09 |
| https://git.kernel.org/stable/c/177b49dbf9c1d8f9f25a22ffafa416fc2c8aa6a3 |
