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 254E3433BB0 for ; Wed, 26 Aug 2026 14:41:01 +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=1787755263; cv=none; b=gyUS0JR759ZOKJiyWFzn9wukGizEjae5D/RyaNBOgZb5K+1jjFLyn5vKrnlMhD72QjZ/X9jCeeDNuVQTOehA2b/bMMEXUcf1O3AFe2lHZSyPFsgV/R8OgqDO6sqFmknUPtG0C/mnfhAQJEABuXy6HNAt5p8U7gdAcccYYyobtww= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787755263; c=relaxed/simple; bh=MS3G1jzkjjF747aQjrHjtNP+WtS4ZreZpXofq5x8y0U=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=EscBRmLQWITFsaAlvpCZug+sn4p6gfaOLjWymyUDQATPiTHoptXgWlW9/+K9jrAwJ0VUDL753QjKmobgT8Wn07zUlCc1TeZfs08a+diuS8KYQ+mVgLMm3etlkWBgTYOGUhVuUNCljAw26hLFuv2ob4Yjq2M4kkY9bRtordnKDWQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=hIuenj8l; 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="hIuenj8l" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 952511F00A3D; Wed, 26 Aug 2026 14:41:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1787755261; bh=bwIVYASbbruNtbJ6z/esvvcRyPQwbLqjJ3+A9bqVM90=; h=From:To:Cc:Subject:Date:Reply-To; b=hIuenj8lWnts55MHIcUIe8+vBs4WKUc/kOp1nATTjWH1gk3OO3u0gfhvWUHBnuYD7 4H/xVdPOQ65BVqq/BKqyJm8kWNclm01SXAdqP7rHt8xAkH2d1crbVcGQGMoEip+jKE bbFNlW84XOEfb2VdmPy0j5EXpx8/1sE7c7Tv0nGg= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80539: drm/amdgpu: disallow multiple FENCE chunks in one submit Date: Wed, 26 Aug 2026 16:37:35 +0200 Message-ID: <2026082605-CVE-2026-80539-ee80@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=3197; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=0aaYs2OSBOnaFDaQ4JsrEv8c86Cx7WdKARVTja2+4pg=; b=owGbwMvMwCRo6H6F97bub03G02pJDFl9vwR/rjepOZ+/Y9Kib9c3XHi2xfrJ9sYlLaoigZk5D zUfGQZt74hlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJ+HsxzPf8k+A9e8bt2cVx AUnXn+UfNFqSNI9hFvO8/oqgeyb5ZsXbpjyonvog7vI8fwA= 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/amdgpu: disallow multiple FENCE chunks in one submit amdgpu_cs_pass1() dispatches on chunk_id once per chunk without rejecting repeated ids. p->uf_bo is a single-slot field, so a submission carrying two AMDGPU_CHUNK_ID_FENCE chunks runs amdgpu_cs_p1_user_fence() twice, and the second run overwrites p->uf_bo with a freshly referenced BO without dropping the reference taken by the first. amdgpu_cs_parser_fini() only unrefs the final p->uf_bo, so every FENCE chunk but the last leaks a BO reference. The leaked BO outlives handle close and process exit. Reject duplicate FENCE chunks the same way commit fec5f8e8c6bc ("drm/amdgpu: disallow multiple BO_HANDLES chunks in one submit") did for p->bo_list. (cherry picked from commit 665b1fc2a1845206408f9a2c6da67101789edb82) The Linux kernel CVE team has assigned CVE-2026-80539 to this issue. Affected and fixed versions =========================== Issue introduced in 4.2 with commit d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and fixed in 6.6.153 with commit 070229262ede37d17c4ea596650deb6e5eb5d106 Issue introduced in 4.2 with commit d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and fixed in 6.12.105 with commit 5f46322e0b84af29e10eb951ff45bd6ea40640de Issue introduced in 4.2 with commit d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and fixed in 6.18.46 with commit 71aa45f7bfe46fbc6f51e7832573ff49b6005fea Issue introduced in 4.2 with commit d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and fixed in 7.1.10 with commit e3ee74d6dbbe409eb99546a7b0a02b2782f9021d Issue introduced in 4.2 with commit d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and fixed in 7.2 with commit 931cd1d1baeae68e8eb2c23bc1f3d8934dca6241 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-80539 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/amd/amdgpu/amdgpu_cs.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/070229262ede37d17c4ea596650deb6e5eb5d106 https://git.kernel.org/stable/c/5f46322e0b84af29e10eb951ff45bd6ea40640de https://git.kernel.org/stable/c/71aa45f7bfe46fbc6f51e7832573ff49b6005fea https://git.kernel.org/stable/c/e3ee74d6dbbe409eb99546a7b0a02b2782f9021d https://git.kernel.org/stable/c/931cd1d1baeae68e8eb2c23bc1f3d8934dca6241