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=1795154309; b=4pCeF0CqNbg2sRm9fzHxtk1HB+A8zTEfa35mlQgkEIcEbYLOQJNNbOa02z0OsqO2Jt9v XMfuQ4cyfVv1GdySGH/OYeYKiyo3wXagAe9lO4s56RTif8+s82PA5QeKYW5nb6K37+nC6 vrN2dHZ4VilXOFC1sATnYarly4kstPHAFcZkxI1lyYw6p0XCKpDN/SD3vKyb6SCLAYb1+ t4NHDHNdCpPbSw8p2GFL4uSwVKkYb8zCCOThOcJah9639rETFbUpnpoLj1VyfR8NHmv1D tTsfZeqWNo5EOGYmuWZbYuqIB/iKIU+6ayXkX18lgw6MDxhvBAyI2S++dR/Uz/ybZMw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154309; 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=bFLfC2IeMctcDHlFeEvZ0M6g7PRP11Uwa5j4UuYm1/w=; b=RpNUL3OIosW3iaRBzT4+tSreN3fWQVx8JouDwhJYdjreqoXRq7KXS9G5wVjm+T4l1VPO 9T9MErwjjiiUz7+DSJ3Ide7ywc48/VmVVq8FGH0xCsWtGnpAIbRr1CGc4MeHypzfGUUg6 iQ5dmVkT5qiPw33pTBH7Kk9HbPFhuZ/2AVn1CmoCnUeukbmRYL40YZlC/JmpDcyX7G3SO UofdDt2UIxXyiPraxMFE4Se5qS+6bEHi5m0l7CzzCdm6T+fynXHlp/vRbJf9dzwHJF6rg Y0CPgjibhAJQC7YOhlcmNa6+ffM5D8aeept7lyBh6G/ZgUOL8lQqO1zA+feAAGObCBQ== 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=SAnoBB8v; 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 E65FE606A320 for ; Fri, 20 Nov 2026 05:58:28 +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=SAnoBB8v Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0F4EB1F000D0; Fri, 20 Nov 2026 05:58:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154308; bh=bFLfC2IeMctcDHlFeEvZ0M6g7PRP11Uwa5j4UuYm1/w=; h=From:To:Cc:Subject:Date:Reply-To; b=SAnoBB8vieGs+amxvTb2zUBXHdcHhD4jq/m8z7kXuKj/XcLFQmHaq/8c4tporvfcV S1FfWivTr/oc2KWnD0Mcy0n8Ua1S1JuWQuTPAxTq0T5jAtV3mYXfXOi4eCYvRxzAeH NXy0dm6mWlFevakqhO67jXr4y1jDGea5oJx0sCOY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99698: mm/cma: accept memory of CMA areas reserved at a fixed address Date: Fri, 20 Nov 2026 06:51:24 +0100 Message-ID: <2026112001-CVE-2026-99698-623a@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=2432; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=qKP0oLpvUXJdt8yrJrUFEE1IeMHGJPBGyrUZj17s3vY=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/73cGbs1nfjDDVbah/MLPWfX7+nY3Wwq8N0tibzfL3 5pt7SveEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABMRcWBYsPTKVnEW5sAjPntO Ncnc6P9z8uLJMoYFK5mc/zL1ritYUjVPtfFgwL+lWxfkAwA= 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 CMA areas reserved at a fixed address CMA areas allocated from memblock have their memory accepted by memblock_alloc_range_nid(), but areas reserved at a fixed address with memblock_reserve() are not. If a fixed CMA area is requested by the cma=@ command line parameter, it may be in regular RAM and on TDX and SEV-SNP guests it must be accepted. Accept the memory of fixed CMA areas as well, so that all CMA areas are accepted regardless of how they were reserved. The Linux kernel CVE team has assigned CVE-2026-99698 to this issue. Affected and fixed versions =========================== Issue introduced in 6.5 with commit 75d090fd167acab4d7eda7e2b65729e877c0fd64 and fixed in 6.18.64 with commit 6b1e545759608795f8c6123cca892073a5e5a38d Issue introduced in 6.5 with commit 75d090fd167acab4d7eda7e2b65729e877c0fd64 and fixed in 7.3.5 with commit 167d6b31a447902c205b34638a6c90b55253f216 Issue introduced in 6.5 with commit 75d090fd167acab4d7eda7e2b65729e877c0fd64 and fixed in 7.4-rc2 with commit f8f9cbc34a309a388c052706f3329d1b52985aa3 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-99698 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/6b1e545759608795f8c6123cca892073a5e5a38d https://git.kernel.org/stable/c/167d6b31a447902c205b34638a6c90b55253f216 https://git.kernel.org/stable/c/f8f9cbc34a309a388c052706f3329d1b52985aa3