| 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: <2025071012-CVE-2025-38293-8e77@gregkh> Date: Thu, 10 Jul 2025 09:42:34 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-38293: wifi: ath11k: fix node corruption in ar->arvifs list From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix node corruption in ar->arvifs list In current WLAN recovery code flow, ath11k_core_halt() only reinitializes the "arvifs" list head. This will cause the list node immediately following the list head to become an invalid list node. Because the prev of that node still points to the list head "arvifs", but the next of the list head "arvifs" no longer points to that list node. When a WLAN recovery occurs during the execution of a vif removal, and it happens before the spin_lock_bh(&ar->data_lock) in ath11k_mac_op_remove_interface(), list_del() will detect the previously mentioned situation, thereby triggering a kernel panic. The fix is to remove and reinitialize all vif list nodes from the list head "arvifs" during WLAN halt. The reinitialization is to make the list nodes valid, ensuring that the list_del() in ath11k_mac_op_remove_interface() can execute normally. Call trace: __list_del_entry_valid_or_report+0xb8/0xd0 ath11k_mac_op_remove_interface+0xb0/0x27c [ath11k] drv_remove_interface+0x48/0x194 [mac80211] ieee80211_do_stop+0x6e0/0x844 [mac80211] ieee80211_stop+0x44/0x17c [mac80211] __dev_close_many+0xac/0x150 __dev_change_flags+0x194/0x234 dev_change_flags+0x24/0x6c devinet_ioctl+0x3a0/0x670 inet_ioctl+0x200/0x248 sock_do_ioctl+0x60/0x118 sock_ioctl+0x274/0x35c __arm64_sys_ioctl+0xac/0xf0 invoke_syscall+0x48/0x114 ... Tested-on: QCA6698AQ hw2.1 PCI WLAN.HSP.1.1-04591-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1 The Linux kernel CVE team has assigned CVE-2025-38293 to this issue. Affected and fixed versions =========================== Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 5.10.239 with commit 6c139015b597e570dd5962934e9f9a2f4cc8ef48 Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 5.15.186 with commit f9507cf2dd0e1ed5028c0e8240da6fe5fd3110d3 Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 6.1.142 with commit b0974ed82e6ad5ff246fd90a5b14f3e7be4f2924 Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 6.6.94 with commit f50ba7e7b607f2d00618799312e7fdb76a1ff48e Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 6.12.34 with commit f5d77d0d41ea7a204d47288d0cf0404a52b5890e Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 6.15.3 with commit 6d6cb27fe146061f2512e904618f5e005bb7bb6a Issue introduced in 5.6 with commit d5c65159f2895379e11ca13f62feabe93278985d and fixed in 6.16-rc1 with commit 31e98e277ae47f56632e4d663b1d4fd12ba33ea8 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-38293 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.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/6c139015b597e570dd5962934e9f9a2f4cc8ef48 https://git.kernel.org/stable/c/f9507cf2dd0e1ed5028c0e8240da6fe5fd3110d3 https://git.kernel.org/stable/c/b0974ed82e6ad5ff246fd90a5b14f3e7be4f2924 https://git.kernel.org/stable/c/f50ba7e7b607f2d00618799312e7fdb76a1ff48e https://git.kernel.org/stable/c/f5d77d0d41ea7a204d47288d0cf0404a52b5890e https://git.kernel.org/stable/c/6d6cb27fe146061f2512e904618f5e005bb7bb6a https://git.kernel.org/stable/c/31e98e277ae47f56632e4d663b1d4fd12ba33ea8
Powered by blists - more mailing lists