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 4F49A13DBBE for ; Fri, 13 Sep 2024 05:31:12 +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=1726205472; cv=none; b=KPZ6GmEj+yW9YohO/6MSA8qkx1d9WNrbb/fL0gHYTyhNMaJahtQ5mjhUD/Ny97RoBBYvqbXCw84aO/D3PWTcwd+SfcJBFSnNYUFPJ8fR5H9ENIvXZg8Vfi1Q2D5uO7yy1pUx036rnlDaw4jVIJdjnM4s/qSqerrG9mKA4vsfD8I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1726205472; c=relaxed/simple; bh=EEqaW+4IzSIQz3bUHlkBjQXpymAZySk/PpFyXFuGyv8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=PnAQ6lCVQ9ckR5bj0IKvsFweOT5O6bxVzvzV3tO+mRlh/5FsP0VtNHfaQi/0ptHuWxb6cVn1wgWhVkZDzc+bvxjoABJO6U4F/aNAxriK436Qs8hyi4b9PdDXH7dLVSINFkzaX1UpRQkMPK9iXKn+tLfg3mtb6XnwVKJ+J4Z3Ryk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=B5QmIgHo; 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="B5QmIgHo" Received: by smtp.kernel.org (Postfix) with ESMTPSA id BB211C4CEC0; Fri, 13 Sep 2024 05:31:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1726205472; bh=EEqaW+4IzSIQz3bUHlkBjQXpymAZySk/PpFyXFuGyv8=; h=From:To:Cc:Subject:Date:Reply-to:From; b=B5QmIgHovihsKnEhs7Ljr9TjrjBj9lV9DJ+AFPtfGsixGvuNwtXr+fyBWVbkwtxHu EYUGnMDems/X1xc1HyPq7Gqpmt4qljFKjGrexe+CiAQsRQAFpu1XAKNDLG2iy7SLmq /4s2EEaCM10k/+QF+r9aeLtWyBb3g48nXjv30CvY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2024-46689: soc: qcom: cmd-db: Map shared memory as WC, not WB Date: Fri, 13 Sep 2024 07:30:50 +0200 Message-ID: <2024091339-CVE-2024-46689-4c19@gregkh> X-Mailer: git-send-email 2.46.0 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=3317; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=EEqaW+4IzSIQz3bUHlkBjQXpymAZySk/PpFyXFuGyv8=; b=owGbwMvMwCRo6H6F97bub03G02pJDGmPz/7fqWpqx7skX0MkZrdzQ5AkQ3hPZO4bz6J3PxSeB BZcbfXoiGVhEGRikBVTZPmyjefo/opDil6Gtqdh5rAygQxh4OIUgImkWTIsOO6x60zZ70nW+T81 T/372KkiH37iC8MczqPiM/lYmvV0fv72fJ4tNzVrd+0FAA== 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: soc: qcom: cmd-db: Map shared memory as WC, not WB Linux does not write into cmd-db region. This region of memory is write protected by XPU. XPU may sometime falsely detect clean cache eviction as "write" into the write protected region leading to secure interrupt which causes an endless loop somewhere in Trust Zone. The only reason it is working right now is because Qualcomm Hypervisor maps the same region as Non-Cacheable memory in Stage 2 translation tables. The issue manifests if we want to use another hypervisor (like Xen or KVM), which does not know anything about those specific mappings. Changing the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC removes dependency on correct mappings in Stage 2 tables. This patch fixes the issue by updating the mapping to MEMREMAP_WC. I tested this on SA8155P with Xen. The Linux kernel CVE team has assigned CVE-2024-46689 to this issue. Affected and fixed versions =========================== Issue introduced in 4.18 with commit 312416d9171a and fixed in 5.4.283 with commit 0ee9594c9743 Issue introduced in 4.18 with commit 312416d9171a and fixed in 5.10.225 with commit f5a5a5a0e95f Issue introduced in 4.18 with commit 312416d9171a and fixed in 5.15.166 with commit eaff392c1e34 Issue introduced in 4.18 with commit 312416d9171a and fixed in 6.1.108 with commit d9d48d70e922 Issue introduced in 4.18 with commit 312416d9171a and fixed in 6.6.49 with commit ef80520be0ff Issue introduced in 4.18 with commit 312416d9171a and fixed in 6.10.8 with commit 62c2d63605ca Issue introduced in 4.18 with commit 312416d9171a and fixed in 6.11-rc6 with commit f9bb896eab22 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-2024-46689 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/soc/qcom/cmd-db.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/0ee9594c974368a17e85a431e9fe1c14fb65c278 https://git.kernel.org/stable/c/f5a5a5a0e95f36e2792d48e6e4b64e665eb01374 https://git.kernel.org/stable/c/eaff392c1e34fb77cc61505a31b0191e5e46e271 https://git.kernel.org/stable/c/d9d48d70e922b272875cda60d2ada89291c840cf https://git.kernel.org/stable/c/ef80520be0ff78ae5ed44cb6eee1525e65bebe70 https://git.kernel.org/stable/c/62c2d63605ca25b5db78a347ed303c0a0a77d5b4 https://git.kernel.org/stable/c/f9bb896eab221618927ae6a2f1d566567999839d