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=1795154228; b=KxyETSWGuiongCRFjcn4VBnyLNLTHViPQ1sc0Ph9jau4RlcrqCWgUXH/rlw7ll2md0u0 dOSNLALhXKceR3xJWFBVVcCd83Frv8fKEErTZA0pRh9CB7R3p4nq5pSya3UdyxZDEekhi FmL6jcGH1QHshhvndpkXYaOfuZQVl/zfv3DJPiHNavtzsDDgeTKDMb6xnX4V4R4gM9035 lKFMDmpesg/nPqgOe9OsQbjsybrcbhlq72ao9uVeAwvfyZKaeNNXLvh90Bd0IoeIupBbl OqB8JE9yy/gMKDR3YtrNKiwkRoKXj6M48DF0A5+LSssaSPfPC8vnIAeHBAN8VHp4bTA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154228; 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=NweKDBBGCh6ToWA8n50295XXLVE40MkMtn+WLbOLS54=; b=DfoQlV3Z9xcEcE8eJrnYQrHUphp6lsssiSfNNv/6sPxfcbXP7fJwDcf2mR8V4VOSdM4R 4n3Y9TK4IPE9qvi+f67ogMPYK5MfDt9HnG4pPNFyBoTDvVfFAYNEY9gahiAdww+DOQ5Om oa5rKQtlpGq0Z024Nou1rSS1QNmtypTHGaaE3HkhlLv9zZKpA5hR8FpB91wacHD4yrUsH l5vTuRviKyPldD3HGW538nFjU4sUYsIYLOkfbDmAHv0iTuE9wOfS1HSe6xebLjYZuRzCE 3hSm39Q6kG7kWkKkCAkpjknvz7hR5TgEkfmjhYJbonyqbA7eL6MDtXC82Jody4/FW2Q== 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=UpJuG4IU; 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 B50EF60A3822 for ; Fri, 20 Nov 2026 05:57:07 +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=UpJuG4IU Received: by smtp.kernel.org (Postfix) with ESMTPSA id 48C3C1F000E1; Fri, 20 Nov 2026 05:57:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154227; bh=NweKDBBGCh6ToWA8n50295XXLVE40MkMtn+WLbOLS54=; h=From:To:Cc:Subject:Date:Reply-To; b=UpJuG4IU1ssZ1L9g5y7DgWVfnj6VIK56YwmR+RzsWk4C16/VAd2fizXswplYgipVt K0zJnVVUWI+dmJQPdg4cvZw1LNg6uPSa0XEOxX4IjYvop4KIc0igkLH8sUhYvn+6yp 19uX5ITookV48K6Bre07drVkEer3w9pZ4Mq/tFqo= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99669: mm/huge_memory: fix truncate racing with PMD zapping Date: Fri, 20 Nov 2026 06:50:55 +0100 Message-ID: <2026112050-CVE-2026-99669-30a2@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=3023; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=/I+Wc2G2q8d5p9BG0Fw7b4EzXRIRzG9t7tIR82bKLfQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/79fNPdeuaM7Tsiv5VGPHotuHbfZY9ogp+VvfV/8Vy CK4qSigI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACbS3cUwv2rx3bMGPJ+87lbk Rm77ZeB65y6nEcP84qUu798WvEv8V7M46nX685T2efZMAA== 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/huge_memory: fix truncate racing with PMD zapping zap_huge_pmd_folio() removes the rmap before calling folio_mark_dirty(). If this was the last mapping, truncation can skip unmapping the folio and proceed without waiting for the PMD lock, racing with dirtying. ifs_set_range_dirty() can oops if MADV_DONTNEED races with ftruncate() on XFS, when we get the folio set dirty after it was found to not be mapped anymore. Move folio_mark_dirty() and folio_mark_accessed() before rmap removal, matching the PTE zap path. This keeps the folio mapped while updating its state, so truncation must wait for the page table lock. Fix generated by an LLM and sent by Chris Mason in private. [ david: simplify comment and description ] The Linux kernel CVE team has assigned CVE-2026-99669 to this issue. Affected and fixed versions =========================== Issue introduced in 7.3 with commit fe6cf984939d8e12cb33a99673c8d026c5135e68 and fixed in 7.3.5 with commit a5786ec7ba7967433207f20214ff75768497a2c9 Issue introduced in 7.3 with commit fe6cf984939d8e12cb33a99673c8d026c5135e68 and fixed in 7.4-rc2 with commit e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4 Issue introduced in 5.10.273 with commit 79d8c89baa10612c1675972a632c65cdbe0936f6 Issue introduced in 5.15.224 with commit 13f4910d81b62a214cdb28b47237198fa96078a2 Issue introduced in 6.1.191 with commit 7a4c3f7b47ba34b021a7747081f330bfb76a4271 Issue introduced in 6.6.160 with commit 6e904f9e8cb0e39f60e1cdbea679f89346a563c2 Issue introduced in 6.12.114 with commit fd720d3906877b3d2118cd480027e4bc6648f0c5 Issue introduced in 6.18.52 with commit effe3cc6d4fdd407457eb30f7b0ef094393f0d64 Issue introduced in 7.2.5 with commit 9435cddf1378d149d826bd7bd1448a44bf96868d 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-99669 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/huge_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/a5786ec7ba7967433207f20214ff75768497a2c9 https://git.kernel.org/stable/c/e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4