From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154311; b=0M2ttgGoxdITa0VBfNOTd3gxw59tGWurWzl7OUwvTqSybGUX3dXvAspK2/d2ZXJsepoP 30TAEIp61Fo7sFgxjgkZGyem8b2mnVBwzsvyE1KL/GUPtm0m11cfrb+SajIKmopi866Sz ShpXwnOXTBt0GHhabxXkHTzly5QCjG5F9qKPeeTYrE2jnzfYiyUZEqyFeducQj+wbP1Oi hNDawoJqr3lSHdFkeqxW4KCJSVbc4NY00JWpzWPYk9cE87lS+M9KIcGxEdsns7UFE9ndP Tl1lIVNxYuQGQlQvzea5KbH3EcMIRKn3hbHjilGBlmDp611bcyk+sGdaMOdljEjb9eA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154311; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=GaLEwH6U+KVEKxl2TaX9+YKzUqLmz3KPUABoVwTOf1w=; b=LgmZ3mCBXP2e/xFS3h4Sb6Dxbt253VhZ7Xaxavn/80k8G5LDOxoGyY9cL/6/6zFOjfzj fLX4m8b2Fv1lpYppJHMKz3D8Sz6RoGopeqDsxjAl0Ue26ua5QzxhZKbe2wl5NE+Yj/7in F898AGpQaMQItNH1GbLsobVMUrVPlbwlp4Na0saNHAXuCj9XxcwCWixsyG5DVyvkz8OjJ i1s7pyPfgVKbv6IW6AuIMuJxveqTR3RGd3jTK+M6U5KEYj81WC91GuGF93+F7PNdfD74i 5AgowQg1xXi178M0HBd2JU0UaWM6EmJP4ZaHLkYKq6NPM8CEjRCpk9keL1nhc+rwqxg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=vSwwEpVH; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C3E2960A261A for ; Fri, 20 Nov 2026 05:58:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=vSwwEpVH Received: by smtp.kernel.org (Postfix) with ESMTPSA id 21CDB1F000D3; Fri, 20 Nov 2026 05:58:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154311; bh=GaLEwH6U+KVEKxl2TaX9+YKzUqLmz3KPUABoVwTOf1w=; h=From:To:Cc:Subject:Date:Reply-To; b=vSwwEpVHODMCT1s6ybcCUjz8Gut6tn9mic2Le22UzfZL72WACvO/SHveuKLBOK/ex Edus3sp6mpsdzXq2Bp5/TH0pVPRwL+ZAzBojhSUUeNZAY3EqD+oms+7a0oZDgmxl9p pxjOZFDCKYHPBUFLainUrpdbq7EMG4ZtLkKUrSPk= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99699: mm/cma: accept memory of multi-range CMA areas Date: Fri, 20 Nov 2026 06:51:25 +0100 Message-ID: <2026112001-CVE-2026-99699-b0bb@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3350; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=JcfXYsUoVIgjBUKB6MbLsk1hkEj4ZgPMKEpRuXA0ows=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/73duszgraj1vq3p3pPUf03s/dnxt7tzJ+ldyx459y 7b4y1Uu7ohlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJPH3NML/S4SmPtHBJmcb7 uULtdq4yG+70OjMs6ExL6t5hn33t1vZ9DhF77yw+yxjQCAA= 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: mm/cma: accept memory of multi-range CMA areas Patch series "mm/cma: accept memory of CMA areas reserved with memblock_reserve()", v1. Pages of allocated CMA areas are released to the buddy allocator with __free_pages(), which does not check for unaccepted memory. This usually works because memblock accepts the memory it allocates. However, multi-range CMA areas, used by hugetlb_cma, and fixed CMA areas requested with cma=@ are reserved with memblock_reserve() and their memory is never accepted. On TDX and SEV-SNP guests the first access to such a page is fatal. To ease the backporting, each case is addressed by a separate patch: - patch 1 accepts the memory of multi-range CMA areas - patch 2 does the same for the fixed CMA areas The second patch won't apply cleanly to 6.6 and 6.12, but I believe the stable team LLMs will take care of that :) This patch (of 2): On systems with unaccepted memory, memblock allocations accept the allocated range, but when cma_declare_contiguous_multi() uses open coded allocation of multiple ranges, it reserves them with memblock_reserve() and they are never accepted. These pages are released to the buddy allocator by cma_activate_area() with __free_pages() that does not check for unaccepted memory, so the first access to such a page in a TDX or SEV-SNP guest is fatal. Accept the memory of each range when it is reserved. The Linux kernel CVE team has assigned CVE-2026-99699 to this issue. Affected and fixed versions =========================== Issue introduced in 6.15 with commit c009da4258f9885c5a3749fc004870db9c0e7a99 and fixed in 6.18.64 with commit 8e2dcdc9806546b4bda6f5904c96f1e5c20d477e Issue introduced in 6.15 with commit c009da4258f9885c5a3749fc004870db9c0e7a99 and fixed in 7.3.5 with commit 89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1 Issue introduced in 6.15 with commit c009da4258f9885c5a3749fc004870db9c0e7a99 and fixed in 7.4-rc2 with commit 5d002001601a163b6c3500cdc098ff66c34f62d8 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-99699 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: mm/cma.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/8e2dcdc9806546b4bda6f5904c96f1e5c20d477e https://git.kernel.org/stable/c/89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1 https://git.kernel.org/stable/c/5d002001601a163b6c3500cdc098ff66c34f62d8