| From bippy-7c5fe7eed585 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-2025-21979: wifi: cfg80211: cancel wiphy_work before freeing wiphy |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| wifi: cfg80211: cancel wiphy_work before freeing wiphy |
| |
| A wiphy_work can be queued from the moment the wiphy is allocated and |
| initialized (i.e. wiphy_new_nm). When a wiphy_work is queued, the |
| rdev::wiphy_work is getting queued. |
| |
| If wiphy_free is called before the rdev::wiphy_work had a chance to run, |
| the wiphy memory will be freed, and then when it eventally gets to run |
| it'll use invalid memory. |
| |
| Fix this by canceling the work before freeing the wiphy. |
| |
| The Linux kernel CVE team has assigned CVE-2025-21979 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.1.57 with commit 3fcc6d7d5f40dad56dee7bde787b7e23edd4b93c and fixed in 6.1.132 with commit 0272d4af7f92997541d8bbf4c51918b93ded6ee2 |
| Issue introduced in 6.5 with commit a3ee4dc84c4e9d14cb34dad095fd678127aca5b6 and fixed in 6.6.84 with commit 75d262ad3c36d52852d764588fcd887f0fcd9138 |
| Issue introduced in 6.5 with commit a3ee4dc84c4e9d14cb34dad095fd678127aca5b6 and fixed in 6.12.20 with commit a5158d67bff06cb6fea31be39aeb319fd908ed8e |
| Issue introduced in 6.5 with commit a3ee4dc84c4e9d14cb34dad095fd678127aca5b6 and fixed in 6.13.8 with commit dea22de162058216a90f2706f0d0b36f0ff309fd |
| Issue introduced in 6.5 with commit a3ee4dc84c4e9d14cb34dad095fd678127aca5b6 and fixed in 6.14 with commit 72d520476a2fab6f3489e8388ab524985d6c4b90 |
| |
| 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-21979 |
| 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/core.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/0272d4af7f92997541d8bbf4c51918b93ded6ee2 |
| https://git.kernel.org/stable/c/75d262ad3c36d52852d764588fcd887f0fcd9138 |
| https://git.kernel.org/stable/c/a5158d67bff06cb6fea31be39aeb319fd908ed8e |
| https://git.kernel.org/stable/c/dea22de162058216a90f2706f0d0b36f0ff309fd |
| https://git.kernel.org/stable/c/72d520476a2fab6f3489e8388ab524985d6c4b90 |
