| 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-49937: wifi: cfg80211: Set correct chandef when starting CAC |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| wifi: cfg80211: Set correct chandef when starting CAC |
| |
| When starting CAC in a mode other than AP mode, it return a |
| "WARNING: CPU: 0 PID: 63 at cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211]" |
| caused by the chandef.chan being null at the end of CAC. |
| |
| Solution: Ensure the channel definition is set for the different modes |
| when starting CAC to avoid getting a NULL 'chan' at the end of CAC. |
| |
| Call Trace: |
| ? show_regs.part.0+0x14/0x16 |
| ? __warn+0x67/0xc0 |
| ? cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211] |
| ? report_bug+0xa7/0x130 |
| ? exc_overflow+0x30/0x30 |
| ? handle_bug+0x27/0x50 |
| ? exc_invalid_op+0x18/0x60 |
| ? handle_exception+0xf6/0xf6 |
| ? exc_overflow+0x30/0x30 |
| ? cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211] |
| ? exc_overflow+0x30/0x30 |
| ? cfg80211_chandef_dfs_usable+0x20/0xaf [cfg80211] |
| ? regulatory_propagate_dfs_state.cold+0x1b/0x4c [cfg80211] |
| ? cfg80211_propagate_cac_done_wk+0x1a/0x30 [cfg80211] |
| ? process_one_work+0x165/0x280 |
| ? worker_thread+0x120/0x3f0 |
| ? kthread+0xc2/0xf0 |
| ? process_one_work+0x280/0x280 |
| ? kthread_complete_and_exit+0x20/0x20 |
| ? ret_from_fork+0x19/0x24 |
| |
| [shorten subject, remove OCB, reorder cases to match previous list] |
| |
| The Linux kernel CVE team has assigned CVE-2024-49937 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 6.1.113 with commit 95f32191e50b75e0f75fae1bb925cdf51d8df0a3 |
| Fixed in 6.6.55 with commit 04053e55dd50741cf6c59b9bbaa4238218c05c70 |
| Fixed in 6.10.14 with commit f4dbfda159e43d49b43003cc3c2914751939035f |
| Fixed in 6.11.3 with commit c628026563f4ea9e0413dd4b69429e4a1db240b1 |
| Fixed in 6.12 with commit 20361712880396e44ce80aaeec2d93d182035651 |
| |
| 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-49937 |
| 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: |
| net/wireless/nl80211.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/95f32191e50b75e0f75fae1bb925cdf51d8df0a3 |
| https://git.kernel.org/stable/c/04053e55dd50741cf6c59b9bbaa4238218c05c70 |
| https://git.kernel.org/stable/c/f4dbfda159e43d49b43003cc3c2914751939035f |
| https://git.kernel.org/stable/c/c628026563f4ea9e0413dd4b69429e4a1db240b1 |
| https://git.kernel.org/stable/c/20361712880396e44ce80aaeec2d93d182035651 |
