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=1795154334; b=003Py9pKeXX+NNTWM9tLxXGRbYWZAQc7xpDP3oBGxogaWgCod3N1p2JVzDuEtkVx6X7c v/rnT5hMzr1yAn+pHu07PW8BzPrDkZuhyqPGRBGkp+prX0zG2K7BitM0hMgEKt4X31jav 8Nb8rzfQXcgiBBJRGOrPsgsU22JkMIk7q5v+ihFq7GruCiowzvtWTUEGGH3biIqCV0+RV o7mtUXShe3snoZfRN3z9V8CbmOJAOfq5ZKeg5Ewno7jDs9pZG90QNOhzoGTBv0KhFVmNd GsvMscCZ1E2I/CQ0hHLMLb+0czpdieA13OU2Ei0eVTbQk0LMPKDziznqbb+00e2oUXw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154334; 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=3IWrLkWjcKJsvEYjcSlLfVVzfqWsrRqf643MJMJv9uU=; b=fcXa0Y1ywsnceIcAd1vRe98ooL4TLPu141TjLVvNUM0oWidtkOMXXowi7+g+CYpCJZ2l cuSE/m9TxFgw//CuT4XJ2B+zdgVszt6mg2Xj6451yIYVjH2VwBOSqxWnCqK2CPf2NTJrh oDkB8aLlgm7yQB/iEj5fNhDpOtK2TpV58wZT61cdNCBPAvupNGu1jx5npsHhHI4Sui/3v 240YY9paFAzJ1wAik9FKmf0u6hlD4rXBhkU+e2jDlPK1PIeYX0IF5fHTqIjP6WExUD6rs I2tf+VAPsHQ+2/iC94FWOlwX+mB9gtNquHT7dfTkJYQwA88OyEOQUGC8HqdOf6YQMjw== 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=dB4TCCyV; 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 CF35960A3803 for ; Fri, 20 Nov 2026 05:58:54 +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=dB4TCCyV Received: by smtp.kernel.org (Postfix) with ESMTPSA id F3E5E1F000C4; Fri, 20 Nov 2026 05:58:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154334; bh=3IWrLkWjcKJsvEYjcSlLfVVzfqWsrRqf643MJMJv9uU=; h=From:To:Cc:Subject:Date:Reply-To; b=dB4TCCyVVHTzxXMaX4Wl10ZsrL+i3nP0mln+TXdFIXuzg1aaT3+cO4AAwEG0ahTGs 5JT0VZT/WIOvVj6OiH+jLee+E9yKRDm/j6+5h521bBPIl3B6xdkAyw09NS5fGnJy1x j9BITXgH8iS2ZhrelauePza3KUaXrl9+HQO4PrZs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99706: mm: fix address wraparound when scanning large folio PTEs Date: Fri, 20 Nov 2026 06:51:32 +0100 Message-ID: <2026112004-CVE-2026-99706-935c@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=2385; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=FsLY2Q7wsBpKJj27ixk894aE/97QnrPVH2qWZ4dT4bQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7/e4L4/fovNMrOK8/+o8CZmleTli67tKvF839P7aP 9dz7u1bHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjARr28Mc/juCGdc/LHqk9mT GV0c2/8vyDn+RZthruyOKTkbfRLV/TjCp3geFzzUZKGzGgA= 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: fix address wraparound when scanning large folio PTEs numa_rebuild_large_mapping() and do_swap_page() can be tricked into generating an address wraparound, crashing the kernel. All that's required is to map a tail page of a large folio close enough to the start/end of the address space to e.g., make unsigned long addr_start = addr - (nr << PAGE_SHIFT); to wrap around. Let's fix it by providing a better helper, folio_scan_range(), that takes care of staying within VMA and page table boundaries while handling possible wraparounds. There are some nasty details, like not being able to use pmd_addr_end() in this context. Add some helpful comments for these cases. The Linux kernel CVE team has assigned CVE-2026-99706 to this issue. Affected and fixed versions =========================== Issue introduced in 6.10 with commit d2136d749d76af980b3accd72704eea4eab625bd and fixed in 7.3.5 with commit f6c17bda9b304795a2c284fb6c8a8eaac6248b80 Issue introduced in 6.10 with commit d2136d749d76af980b3accd72704eea4eab625bd and fixed in 7.4-rc2 with commit f681d4580d5c3c749f623cda722a21aefd3147b3 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-99706 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/memory.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/f6c17bda9b304795a2c284fb6c8a8eaac6248b80 https://git.kernel.org/stable/c/f681d4580d5c3c749f623cda722a21aefd3147b3