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 9DE44224AF9 for ; Sun, 19 Jul 2026 15:03: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=1784473410; cv=none; b=QkkoQCLmJvxDeituqaiByGEyHUUDy4wh6iWa52z8LWP39hByV60C3RZduCvtSH0A6nxJyXxOvaT8O2fHBoN1zZFTr2OGRKs9N+x0iDzZb6r4yqagxSeE3cUN1A1XSlXkkvPe6UirJ/a8sgM16QRx8LJqnSFpjWuIcIrAaqoaOQM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784473410; c=relaxed/simple; bh=pOm8/PhzlioWxd5x0LXHOyVIZWBhG879W+6OfZ33kRU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=t+ulnaV2uw4kGVnZ1stIYu7NJRv5SFoHSgzpSrZT58ca1ahkTO7fvE5htGg/lmJkNTzCPsWA0bb1rIpoqRHXWaHFzrOW8yDimX1R3hUchWvwyylwH6HOzm1YCupfPUwTf/A4aHTb8kc7UaHWP2bbm4Mg0Sg+aQQkb1DDNtWFeSA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=Xioercqs; 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="Xioercqs" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0756E1F00A3A; Sun, 19 Jul 2026 15:03:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784473409; bh=ss/4GAW17hevCY0E2GU80dd2bL+yHoduPQlmZtbFJQI=; h=From:To:Cc:Subject:Date:Reply-To; b=Xioercqsb2WakTcfwuT4d5hLpnr4Ys3tiSwQEaEeG7FWDrxfWbDkwSYH/WmsTNOnv w5PnbBIwhcaS8A6cDal/bYIkpvHEcWJ1hwMOoWO0tlSDeBOqbPxIvucjfzP2/C2/t+ BWHf2/6pzYaYin7mg9HxAdFImes/EBczmh403J8k= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64008: accel/rocket: fix UAF via dangling GEM handle in create_bo Date: Sun, 19 Jul 2026 16:57:48 +0200 Message-ID: <2026071908-CVE-2026-64008-8d40@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=2902; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=9y8Kf28Fq5zvTOtaGkRDLhkh+CxgruRiB0L6/WkBuXI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkxTzvSTN51/ha+Kqz2ecUxz0gRx//fluoov3ZtWdfyJ 5a5UFm0I5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACYi9YxhfqqZgtoe3w/37pjs Ft66eV7MiiqeHwzz1GadypyX+KUtTr3yvPep9xwnTxfeBAA= 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: accel/rocket: fix UAF via dangling GEM handle in create_bo rocket_ioctl_create_bo() inserts a GEM handle into the file's IDR via drm_gem_handle_create() early on, then performs several operations that can fail (sgt allocation, drm_mm insert, iommu_map). If any fail after the handle is live, the error path calls drm_gem_shmem_object_free() which kfree's the object without removing the handle from the IDR. This leaves a dangling handle pointing to freed slab memory. Any subsequent ioctl using that handle (PREP_BO, FINI_BO, SUBMIT) calls drm_gem_object_lookup() and dereferences freed memory (UAF). Fix by moving drm_gem_handle_create() to after all fallible operations succeed, matching the pattern used by panfrost, lima, and etnaviv. Also fix drm_mm_insert_node_generic() whose return value was silently overwritten by iommu_map_sgtable() on the next line. Add the missing error check. [tomeu: Move handle creation to the very end] The Linux kernel CVE team has assigned CVE-2026-64008 to this issue. Affected and fixed versions =========================== Issue introduced in 6.18 with commit 658ebeac33517bd3169d4b65ed801e9065d0211a and fixed in 6.18.35 with commit 18abd88d19ea195e2e1547fca0970c2f91d77a42 Issue introduced in 6.18 with commit 658ebeac33517bd3169d4b65ed801e9065d0211a and fixed in 7.0.12 with commit 451f1ccbbdb7b65021646704b15902655f8d228a Issue introduced in 6.18 with commit 658ebeac33517bd3169d4b65ed801e9065d0211a and fixed in 7.1 with commit f706e6a4ce75585af979aec3dcbdce68bc76306b 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-64008 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/accel/rocket/rocket_gem.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/18abd88d19ea195e2e1547fca0970c2f91d77a42 https://git.kernel.org/stable/c/451f1ccbbdb7b65021646704b15902655f8d228a https://git.kernel.org/stable/c/f706e6a4ce75585af979aec3dcbdce68bc76306b