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=1795154415; b=U8fjvRCF91CkRAI1Xq6XeX/mOna3ZN14sLt1cNGzpbxRgGVuPcijOuGOs0TZE7L31r2a vpnnxTlyi9UZdARQvXQI1goF5QWZyxeT7YsmK4z9yf13O584RJz8wMuThoY+RCWI57310 jmIKCGwrZ7NdLndftLElmKuPpjSkG8B0UIG48R/MkIFHBSBdCbhcW+NMeWA38Gwk/xQHa TPtUJn9XN5bC56pI29YzYyaYSbJeasPbV9Ls/sMA4p+CmO7M0wN9oELPyTFWBReb4yaQF sNXCeXzYrDIk5SyrUusNDUd7MlOXoas9pZid/EuLx35u2ssLXav4FiqhCvYzcko5K9Q== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154415; 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=yhNabyjqvEPQi3qOI6EZrge/6poQIIiS2Mgft/6nn8w=; b=QKCOxU+s8N3zdvBDQ/zkYopDfZpT152j0Buz/62kTlD4dsIuyZyFyIAOfGKFKmTbw43c z9KD/BYzkAotmpDXK26iseDLLqKB+StkKckzpiBgrZPJQvrNBGtEyzgrpVLbIPsAE+heP enNmdwiKWgN1u60tvVJwQTOUHz33faiH5J7NXjNdTA9DKGwNLcRJ33l2Hu9tkFphZ0Zdl SJWamS7TENZMiR6XjZtjp8kZCQeo7SlJ6x3VdUDh1JUeKh+cWdpN7MepK9Hat6HJPZTJ6 P9630sfw+N7uCrbynvloUTkkC5wldW0gkoZtce4JPoe72tnZScrnSter11r2lZKFm4Q== 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=TZYRozdX; 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 F2BFA606A526 for ; Fri, 20 Nov 2026 06:00:14 +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=TZYRozdX Received: by smtp.kernel.org (Postfix) with ESMTPSA id 02C341F000D0; Fri, 20 Nov 2026 06:00:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154414; bh=yhNabyjqvEPQi3qOI6EZrge/6poQIIiS2Mgft/6nn8w=; h=From:To:Cc:Subject:Date:Reply-To; b=TZYRozdXNZXyLZzGE7rzeKFrzuCSlf49WsWOubiVaebcnrXHZAgHXnZypDJkbeOLQ JSE3FHNRO2iutuO+jFP60T88rRjGJcQMHvZA2u2klr2uwHaP3PCZ/zf/L94PQ2W397 upJW8ubzcQp9HBllW3oKPC080L59mf37ItsE+fbI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99735: mm/mglru: don't use stack pointers when walking PUD and PMD tables Date: Fri, 20 Nov 2026 06:52:01 +0100 Message-ID: <2026112015-CVE-2026-99735-21d2@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=3343; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=3V8xC+hJY5lfsacP3RXvUEeiTeO3AferNu9XbglHFp0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/709XnqL7bnfDqWUbVbPvKrGLbNDUe7cwZctLXrnrO g0nltV2dcSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEJmQzzHe81nTixuoz3eUP vsS+fhwz9eLCg6oMC6Y+bt97P3nfwaz4ulYfIXmdyCmHdgMA 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/mglru: don't use stack pointers when walking PUD and PMD tables MGLRU passes stack copies of page-table entries in walk_pud_range() and walk_pmd_range() when walking to the next level. These copies can become stale when khugepaged or MADV_DONTNEED (CONFIG_PT_RECLAIM) removes a PTE table concurrently. This pattern dates back to commit bd74fdaea146 ("mm: multi-gen LRU: support page table walks"). Likely, earlier locking masked the latent bug. Later changes exposed it: commit 1d65b771bc08 ("mm/khugepaged: retract_page_tables() without mmap or vma lock") allowed concurrent retraction, and commit cf4a65539c13 ("memcg-v1: no need for memcg locking for MGLRU") dropped the walker's outer RCU protection. The fix is simple, so just fix the original commit so we don't have to speculate. To fix it, pass the actual PMD/PUD pointers. This restores the RCU-protected lookup and validation against the live PMD. Note that the PUD handling is required as well to handle folded page tables correctly in all cases. Fix generated by an LLM and sent by Josef Bacik in private. [ david: handle walk_pud_range() as well, clarify+simplify description, adjust Fixes: ] The Linux kernel CVE team has assigned CVE-2026-99735 to this issue. Affected and fixed versions =========================== Issue introduced in 6.1 with commit bd74fdaea146029e4fa12c6de89adbe0779348a9 and fixed in 6.12.118 with commit a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e Issue introduced in 6.1 with commit bd74fdaea146029e4fa12c6de89adbe0779348a9 and fixed in 6.18.64 with commit 4b428d9d24e303f92819119c66858f5de38bbc78 Issue introduced in 6.1 with commit bd74fdaea146029e4fa12c6de89adbe0779348a9 and fixed in 7.3.5 with commit 4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3 Issue introduced in 6.1 with commit bd74fdaea146029e4fa12c6de89adbe0779348a9 and fixed in 7.4-rc2 with commit 65a9bf08a3e4d6e58df211ed900c16bafb79b267 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-99735 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/vmscan.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/a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e https://git.kernel.org/stable/c/4b428d9d24e303f92819119c66858f5de38bbc78 https://git.kernel.org/stable/c/4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3 https://git.kernel.org/stable/c/65a9bf08a3e4d6e58df211ed900c16bafb79b267