| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025122435-CVE-2023-54025-68db@gregkh> Date: Wed, 24 Dec 2025 11:57:09 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-54025: wifi: rsi: Do not configure WoWlan in shutdown hook if not enabled From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: Do not configure WoWlan in shutdown hook if not enabled In case WoWlan was never configured during the operation of the system, the hw->wiphy->wowlan_config will be NULL. rsi_config_wowlan() checks whether wowlan_config is non-NULL and if it is not, then WARNs about it. The warning is valid, as during normal operation the rsi_config_wowlan() should only ever be called with non-NULL wowlan_config. In shutdown this rsi_config_wowlan() should only ever be called if WoWlan was configured before by the user. Add checks for non-NULL wowlan_config into the shutdown hook. While at it, check whether the wiphy is also non-NULL before accessing wowlan_config . Drop the single-use wowlan_config variable, just inline it into function call. The Linux kernel CVE team has assigned CVE-2023-54025 to this issue. Affected and fixed versions =========================== Issue introduced in 5.7 with commit 16bbc3eb83728c03138191a5d23d84d38175fa26 and fixed in 5.10.188 with commit b2aeb97fd470206e67f7b3b4a3e68212a13f747b Issue introduced in 5.7 with commit 16bbc3eb83728c03138191a5d23d84d38175fa26 and fixed in 5.15.121 with commit 4391fa180856ff84a2cef4a92694a689eebb855e Issue introduced in 5.7 with commit 16bbc3eb83728c03138191a5d23d84d38175fa26 and fixed in 6.1.39 with commit eb205a06908122f50b1dd1baa43f7c8036bfc7dc Issue introduced in 5.7 with commit 16bbc3eb83728c03138191a5d23d84d38175fa26 and fixed in 6.3.13 with commit 1b51236aa49a0564280bd45c94118cab6d9b0fbd Issue introduced in 5.7 with commit 16bbc3eb83728c03138191a5d23d84d38175fa26 and fixed in 6.4.4 with commit b601468539c1d97539097bfc87ad11f1704b7eb7 Issue introduced in 5.7 with commit 16bbc3eb83728c03138191a5d23d84d38175fa26 and fixed in 6.5 with commit b241e260820b68c09586e8a0ae0fc23c0e3215bd 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-2023-54025 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/rsi/rsi_91x_sdio.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/b2aeb97fd470206e67f7b3b4a3e68212a13f747b https://git.kernel.org/stable/c/4391fa180856ff84a2cef4a92694a689eebb855e https://git.kernel.org/stable/c/eb205a06908122f50b1dd1baa43f7c8036bfc7dc https://git.kernel.org/stable/c/1b51236aa49a0564280bd45c94118cab6d9b0fbd https://git.kernel.org/stable/c/b601468539c1d97539097bfc87ad11f1704b7eb7 https://git.kernel.org/stable/c/b241e260820b68c09586e8a0ae0fc23c0e3215bd
Powered by blists - more mailing lists