From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 828D049BD92 for ; Thu, 24 Sep 2026 15:11:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790262697; cv=none; b=BsRX/uoM91YSjhSIm7aWE2bBZnnJTHDJqXjos5daC/u6JZB3fS7H0HazuQKbEGUS9sBznJYTrUYDwcNUtWqmfJwtpRmoIpu5J0+J/LUe5hnxHbO/r3gDd8EztiGLU/TstQ2P9DTl1LsQ2F0HVJf889zOBDIi9aT8x9PfHz+eiTM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790262697; c=relaxed/simple; bh=BgeT1HJlMriiA6DVlW2E6KS1yNBm3TKu7XsE0bqm3r8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=JbGp4PoIKesff6sI4Fan+uFBvtTPLExrBa1lz/UtGamE3RhoCPp8T/H7+6/a9BXPyaNvYTCW0cHZByjKDW78KETGwoezNrV4U1BMlNfzR+7bXnvPsG3Iu1tzWuEf7c/QqU/37eWfXUwvStcFcymdXnrq3m0qhP2+KbczMEPfRiQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=vmvFYBKc; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="vmvFYBKc" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 291361F000FF; Thu, 24 Sep 2026 15:11:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1790262696; bh=QPt8t9HFAbHgSSvaiM8irLiZjwMZhRSagfWOINPSwY4=; h=From:To:Cc:Subject:Date:Reply-To; b=vmvFYBKc0Hk5ytxstpAMG7dCv0jySPkQW8BqCdUNXze+W1hjYdmItpJgQizRxc3Kn LYXZ/IAlouzIPX1+TFJ74Cppv6xMRtjTH2TGRpQliZdbzrhyhCnsa5TqwHsscNu2Mm Df20aFEpcpHfpi39m9ekKy8mzGLxkoF5McY90zMU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-93217: mm/madvise: skip device-private PMDs in cold and pageout walks Date: Thu, 24 Sep 2026 17:10:53 +0200 Message-ID: <2026092445-CVE-2026-93217-e0ae@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2797; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=uiG9Xp2nxjXt1lnaMvThCyC3U+BGcP6GrvFNdoaC2P8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlbbUs58o6evM/y7Ys50+UdFxhOVbP22lrM/XA6OHfi1 4MN9dMyOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAitVwMC07L/ZeqU03q4Oe/ uVe8O+av3p3zExjmWfk1HzvyYIHbHJnZHydeaBDX+y2mBwA= 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/madvise: skip device-private PMDs in cold and pageout walks madvise_cold_or_pageout_pte_range() takes pmd_trans_huge_lock(), whose pmd_is_huge() check returns true for a device-private PMD. The subsequent !pmd_present() branch has a VM_BUG_ON() asserting migration is the only allowed non-present case; a device-private PMD trips it. Skip device-private PMDs in that non-present branch and continue to huge_unlock before calling pmd_folio(). Downgrade the check to VM_WARN_ON_ONCE() so an unexpected PMD softleaf logs a warning rather than panicking. Drop the thp_migration_supported() guard: it expands to IS_ENABLED(CONFIG_ARCH_SUPPORTS_PMD_SOFTLEAF), and both pmd_is_migration_entry() and pmd_is_device_private_entry() already return false when that config is not selected, so the guard suppresses only the case where the warning would already be silent. Potential trigger: an HMM-based GPU driver races with madvise(MADV_COLD)/MADV_PAGEOUT: pmd_trans_huge(*pmd) reads true, then migrate_vma_pages() flips the PMD to a device-private entry before the PMD lock is acquired. The Linux kernel CVE team has assigned CVE-2026-93217 to this issue. Affected and fixed versions =========================== Issue introduced in 6.19 with commit 368076f52ebeecd33e10a9f80905d7508b6b6149 and fixed in 7.2.4 with commit 5c0d7b658cda62cd17cb3652783386d5608030ef Issue introduced in 6.19 with commit 368076f52ebeecd33e10a9f80905d7508b6b6149 and fixed in 7.3-rc1 with commit d4b76d0b03cb49611312ecc4bcfb55ccdf0843e2 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-93217 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/madvise.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/5c0d7b658cda62cd17cb3652783386d5608030ef https://git.kernel.org/stable/c/d4b76d0b03cb49611312ecc4bcfb55ccdf0843e2