From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A1D8F1AAA2C for ; Wed, 26 Feb 2025 01:58:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740535116; cv=none; b=MHrlTEMSIhY2ioXYrZNjTR0/F2PrG6Ma5PWFt7XOjAYU9lQGSE+yE5xPGMm2Iz1fVmd5zJwDbR75uDZ5JZk2jhf5AUWtV0paQhPPnVCMwE5Kf0Vmr2CRGs1yit4i8bIWoqZ11MDNXsl+ziEBNhyd/ha+eqWe3w1gOBbKJebpoNE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740535116; c=relaxed/simple; bh=oyLjeM1C1hn9tlpiE69CPWYt2M9t1+lI8EJo7J/NtMk=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=D8CnXOIdlyD5fWcrA35UzAiDFJ2y6CDxlJnq/dfjy6w3a7zcD8jZpkZy2VP9Pn8y5P+EyhZelh3i0ZaJU1GSEA9luVx1D8tIrHc82XDIFhfBDqK3fsdTQYxQXHoZDqnIc7TkcWn0ktXhJnoKf0dh91M6YGdSKI5gYHRh9JPnXLE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=mqORm2mt; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="mqORm2mt" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 74560C4CEDD; Wed, 26 Feb 2025 01:58:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740535116; bh=oyLjeM1C1hn9tlpiE69CPWYt2M9t1+lI8EJo7J/NtMk=; h=From:To:Cc:Subject:Date:Reply-to:From; b=mqORm2mtnCzctAHZhY19HGSD5QuAzsdLVzVcMAGuwkd2rWh5Al3YVA9LyZ1/wXR+z lDDal3llQATUOv30u3Aj1GXm/TOBAc3IbD+khFfu3VRqgODHDZtQ0aAYP/u9+P+nsZ i8l4H10b2wX5d9NcX7zvni5TWznewcnyj76UgJdo= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49132: ath11k: pci: fix crash on suspend if board file is not found Date: Wed, 26 Feb 2025 02:55:37 +0100 Message-ID: <2025022605-CVE-2022-49132-e49f@gregkh> X-Mailer: git-send-email 2.48.1 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=3954; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=oyLjeM1C1hn9tlpiE69CPWYt2M9t1+lI8EJo7J/NtMk=; b=owGbwMvMwCRo6H6F97bub03G02pJDOn7Smx3+706NeXugR3vn1h+XM1z5BdjhuqJn8WcJwWWZ RluTD72sSOWhUGQiUFWTJHlyzaeo/srDil6GdqehpnDygQyhIGLUwAm0ujCsOBIVspcXc0Nxvn/ r3useb/68c9dHOsYFqxlO6cZ9O3MzRCLIo/KNRVTawSuqAIA X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: ath11k: pci: fix crash on suspend if board file is not found Mario reported that the kernel was crashing on suspend if ath11k was not able to find a board file: [ 473.693286] PM: Suspending system (s2idle) [ 473.693291] printk: Suspending console(s) (use no_console_suspend to debug) [ 474.407787] BUG: unable to handle page fault for address: 0000000000002070 [ 474.407791] #PF: supervisor read access in kernel mode [ 474.407794] #PF: error_code(0x0000) - not-present page [ 474.407798] PGD 0 P4D 0 [ 474.407801] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 474.407805] CPU: 2 PID: 2350 Comm: kworker/u32:14 Tainted: G W 5.16.0 #248 [...] [ 474.407868] Call Trace: [ 474.407870] [ 474.407874] ? _raw_spin_lock_irqsave+0x2a/0x60 [ 474.407882] ? lock_timer_base+0x72/0xa0 [ 474.407889] ? _raw_spin_unlock_irqrestore+0x29/0x3d [ 474.407892] ? try_to_del_timer_sync+0x54/0x80 [ 474.407896] ath11k_dp_rx_pktlog_stop+0x49/0xc0 [ath11k] [ 474.407912] ath11k_core_suspend+0x34/0x130 [ath11k] [ 474.407923] ath11k_pci_pm_suspend+0x1b/0x50 [ath11k_pci] [ 474.407928] pci_pm_suspend+0x7e/0x170 [ 474.407935] ? pci_pm_freeze+0xc0/0xc0 [ 474.407939] dpm_run_callback+0x4e/0x150 [ 474.407947] __device_suspend+0x148/0x4c0 [ 474.407951] async_suspend+0x20/0x90 dmesg-efi-164255130401001: Oops#1 Part1 [ 474.407955] async_run_entry_fn+0x33/0x120 [ 474.407959] process_one_work+0x220/0x3f0 [ 474.407966] worker_thread+0x4a/0x3d0 [ 474.407971] kthread+0x17a/0x1a0 [ 474.407975] ? process_one_work+0x3f0/0x3f0 [ 474.407979] ? set_kthread_struct+0x40/0x40 [ 474.407983] ret_from_fork+0x22/0x30 [ 474.407991] The issue here is that board file loading happens after ath11k_pci_probe() succesfully returns (ath11k initialisation happends asynchronously) and the suspend handler is still enabled, of course failing as ath11k is not properly initialised. Fix this by checking ATH11K_FLAG_QMI_FAIL during both suspend and resume. Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 The Linux kernel CVE team has assigned CVE-2022-49132 to this issue. Affected and fixed versions =========================== Fixed in 5.15.34 with commit fed4cef115ab21a18faf499b3fa9b9a4b544f941 Fixed in 5.16.20 with commit f3c5ef433da82d257337424b3647ce9dcb37d4b5 Fixed in 5.17.3 with commit aeed776c00e804a0f7896db39c7c661cea34ee1f Fixed in 5.18 with commit b4f4c56459a5c744f7f066b9fc2b54ea995030c5 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-2022-49132 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/pci.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/fed4cef115ab21a18faf499b3fa9b9a4b544f941 https://git.kernel.org/stable/c/f3c5ef433da82d257337424b3647ce9dcb37d4b5 https://git.kernel.org/stable/c/aeed776c00e804a0f7896db39c7c661cea34ee1f https://git.kernel.org/stable/c/b4f4c56459a5c744f7f066b9fc2b54ea995030c5