From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 9A50B374A0E for ; Thu, 17 Sep 2026 16:27:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789662422; cv=none; b=EuImb4P1/uskWFQAXYZRuZpQHXmjNAij8x3yJDZQhsKYoPWX2nuKZ/kqGtakRLD/Eddbss9MKgVgWlBds7F1HDe3Xt5+TWVhFGmlmmT6/tZQqpJzOlDwGupZBHVkxFrvW/+hX83J3sSuFGZ8g8uxN+c1987cZqssnhnvoioC//I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789662422; c=relaxed/simple; bh=BL40vM3BL9JWGiRK0sio2sVepOkzeeZRseSS7oWyKlg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=u4c4ojD66U9aQUQUA5Zmn4eATN6+B/ocIDaYN+vGRRhMEaxrCqAIRamrvmMFq98E0QsJDewu0fk631lVIpDkl/BCb/cxMKRrLGF10M7dgvU16+od5lBAh5GyLRyS43SMXo45Jr9GxghKAs44+Cpl4D90xmLh95ifTIEhxXpfPXU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=PpRlsGe/; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="PpRlsGe/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EDC021F000FF; Thu, 17 Sep 2026 16:27:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789662421; bh=dxPX1hbHkQlVC0wRxjz5dTfXnRJWJlUMRm/yiciF5bc=; h=From:To:Cc:Subject:Date:Reply-To; b=PpRlsGe/HV8KiLKHW2DKMI4UjIwcQS0tsH1IxJJW0o7zFSMxYmwnqPCZb3WH3ljMA YBqQtweWKMXWQZ+J+GkM2HV0cXJVpUp1U63h2olSE3A0EuDuBrc7EtJ6pwusaj0wX7 l9ayv45MQPH/zG9N7OnD9zJJJy5VLk2+cfZeEiAE= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-90348: wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump Date: Thu, 17 Sep 2026 17:12:58 +0100 Message-ID: <2026091703-CVE-2026-90348-b295@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4533; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=kN46QKXpZCkuYtie+4jE4S/tjIust1W2IKQBID9pz9E=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlrBBaEe5Zfjy+cHS7iu/FllPGr9lUTS8vOMU3ecWrF2 dwXl4wCOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAi7d8Z5pc9+jFtv3xJo+pO O9GO5YZpbA7K7xjmSqWZpqmYOidP8I9PN+Y30z208N90AA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump On WCN3990/SNOC the MSA region is mapped with devm_memremap(MEMREMAP_WT). On arm64 such a mapping is not Normal-cacheable, so unaligned accesses to it are not permitted. ath10k_msa_dump_memory() copies the region with a plain memcpy(), whose optimized __pi_memcpy_generic implementation issues wide/unaligned loads. This triggers an alignment fault (FSC=0x21) Oops in ath10k_snoc_fw_crashed_dump() while collecting the devcoredump: Unable to handle kernel paging request ... FSC=0x21: alignment fault pc : __pi_memcpy_generic lr : ath10k_snoc_fw_crashed_dump [ath10k_snoc] The Oops both leaves the firmware RAM dump buffer zeroed (no dump is captured) and crashes the kernel, which in turn breaks modem SSR recovery. Use memcpy_fromio(), which only performs accesses that are valid for such a device-memory mapping. The generic memcpy_fromio() implementation aligns the source before issuing word-sized reads and stores the destination with put_unaligned(), so it is also safe for the coherent DMA allocation used on the non-reserved-memory path. ath11k and ath12k use the same pattern when copying target memory into crash dumps, so call it unconditionally here too. The MEMREMAP_WT pointer is a plain void *, so an explicit __iomem cast is needed; use __force to keep sparse happy. Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.3.3.7.c5-00107-QCAHLSWMTPL-1 The Linux kernel CVE team has assigned CVE-2026-90348 to this issue. Affected and fixed versions =========================== Issue introduced in 5.5 with commit 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and fixed in 5.10.270 with commit e5bc3658da9c8a535e3fa5c0c875b2a456954e81 Issue introduced in 5.5 with commit 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and fixed in 5.15.221 with commit fed1f662c9f9fd19eeab6c01966b7b5a33804420 Issue introduced in 5.5 with commit 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and fixed in 6.1.188 with commit 838cab267ce9a975776e022f25094f8cbe1625d2 Issue introduced in 5.5 with commit 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and fixed in 6.6.157 with commit eb946595a58decdb4cab1b5f3c972ae66f41f1c8 Issue introduced in 5.5 with commit 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and fixed in 6.12.110 with commit 152e894e90716163c646d70f86b3afeb70442783 Issue introduced in 5.5 with commit 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and fixed in 6.18.52 with commit 7039825a7479df637c4f5d546cb0e1cec18cd8e1 Issue introduced in 5.5 with commit 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and fixed in 7.2.6 with commit 045d1bfb72d2631ab9ec74afa491aa788ebb57aa Issue introduced in 5.5 with commit 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and fixed in 7.3-rc1 with commit 4f25071afe9218aaae1c63fbf75e229aa6405319 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-2026-90348 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/ath10k/snoc.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/e5bc3658da9c8a535e3fa5c0c875b2a456954e81 https://git.kernel.org/stable/c/fed1f662c9f9fd19eeab6c01966b7b5a33804420 https://git.kernel.org/stable/c/838cab267ce9a975776e022f25094f8cbe1625d2 https://git.kernel.org/stable/c/eb946595a58decdb4cab1b5f3c972ae66f41f1c8 https://git.kernel.org/stable/c/152e894e90716163c646d70f86b3afeb70442783 https://git.kernel.org/stable/c/7039825a7479df637c4f5d546cb0e1cec18cd8e1 https://git.kernel.org/stable/c/045d1bfb72d2631ab9ec74afa491aa788ebb57aa https://git.kernel.org/stable/c/4f25071afe9218aaae1c63fbf75e229aa6405319