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 A0C0530C16F for ; Wed, 24 Jun 2026 16:32:29 +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=1782318750; cv=none; b=TLS82d6gHWCjPgARe+gsnVys5mEYs+9JWasaA4iJjA8Jf1inqEFS/LZomSEO77V+cJMYaB33UuRo2HosIb2KX38nulpEHVQl3FcpPoPGLINqf3aZyTS9N1lR2d5HJGBrLpFhJ87O0KxLyjYsu3dGu7bLLIIVM7l4RW1ddwIlxWA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782318750; c=relaxed/simple; bh=1iyUmZXGna9E1T7yrX3u9q0/zy0gvCIR1fyOakFG+qA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=rpqdYPHqikAG6M8wdTX9xF95hbw9MAZBEqYcgp4L+Ie9cpxx7gDXGEwmQ3dkQfXL4mKu8VmpA2GfUK9JNEN+D68v3Ks1MCiRGEVen3/MPjWIXc66A7OIH6GowCBG72nCcfCPYukb4Nt/xtSDGILB7HRmaCY8v+JfPs+pZvKk2jo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=KK+72eLh; 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="KK+72eLh" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A42601F00A3D; Wed, 24 Jun 2026 16:32:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1782318749; bh=e9XR3Ou/daNd8vu+ruBnrFNMPQhdVgvAqNhzcLdVeMM=; h=From:To:Cc:Subject:Date:Reply-To; b=KK+72eLhIZ5gHZ/xQU5GtKghAbIenYAikydJRUXQb50U/wiCYWCPeuEwYUtt/aqzF V+qlLewVUpTfHjPyJS+wyEr+liR7lsjALk95eLXgvdMJ0PcvBveXjt/3w2GE3rtdyp BGeDV7gFL6ZX1Gnq3avE5BKxYdhRK5L8c8Uh7kg4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-52965: drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure Date: Wed, 24 Jun 2026 17:29:49 +0100 Message-ID: <2026062438-CVE-2026-52965-b15c@gregkh> X-Mailer: git-send-email 2.54.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=2771; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=AAEy5+QBWv4ZmYO2ZI6Bha9s+tVWdhkLOSQxeJWbstg=; b=owGbwMvMwCRo6H6F97bub03G02pJDFk2rJ/03Odf7Iu7NT1d6jD3awWRV/v6BTK31yvf3NrIv vVF09PgjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZgI0zWG+VXdrxd+nMmwILdQ NrygqXZq0AVbIK9VfDLz+jNPXyzZ0DGXZ5V5SFDTz8UA 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: drm/ttm: Fix ttm_bo_swapout() infinite LRU walk on swapout failure When ttm_tt_swapout() fails, the current code calls ttm_resource_add_bulk_move() followed by ttm_resource_move_to_lru_tail() to restore the resource's bulk_move membership. However, ttm_resource_move_to_lru_tail() places the resource at the tail of the LRU list which, relative to the walk cursor's hitch node (placed immediately after the resource when it was yielded), puts the resource *in front of the* the hitch. The next list_for_each_entry_continue() from the hitch finds the same resource again, causing an infinite loop. Fix by deferring del_bulk_move to the success path only. On the success path, TTM_TT_FLAG_SWAPPED has just been set by ttm_tt_swapout() but the resource is still tracked in the bulk_move range, so ttm_resource_del_bulk_move()'s !ttm_resource_unevictable() guard would incorrectly skip the removal. Introduce ttm_resource_del_bulk_move_unevictable() which bypasses that guard. The Linux kernel CVE team has assigned CVE-2026-52965 to this issue. Affected and fixed versions =========================== Issue introduced in 6.13 with commit fc5d96670eb2540d2572a14351e82ffe45d5ac11 and fixed in 7.0.10 with commit 0124a09e3e5f5f6080efe9663b27af27933f8382 Issue introduced in 6.13 with commit fc5d96670eb2540d2572a14351e82ffe45d5ac11 and fixed in 7.1 with commit b2ed01e7ad3de80333e9b962a44024b094bc0b2b 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-52965 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: drivers/gpu/drm/ttm/ttm_bo.c drivers/gpu/drm/ttm/ttm_resource.c include/drm/ttm/ttm_resource.h 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/0124a09e3e5f5f6080efe9663b27af27933f8382 https://git.kernel.org/stable/c/b2ed01e7ad3de80333e9b962a44024b094bc0b2b