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 352924F4749 for ; Wed, 16 Sep 2026 10:33:52 +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=1789554845; cv=none; b=eeHjYVxEurWqhb/ikiyF53YsiENBopG6GCJXI6y6O+VVgkTae4kPvPJ+pzOgQFx630A7/80jeRRQe+RY5ymXpMWFsyu6Ef7V03lBoYiprC0ikZRUEbXVPwelaFw7Oko+pP9hq3cuQAuUkS9nqX1+mBiFChUsk1La0zhBsfCE0Qo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789554845; c=relaxed/simple; bh=I8dUk74vAXf6/dQL3k6ahQY628UOOCnKLPYiUlibXvs=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=UaPUhmIsTcHlop1RipTziQbA6wLo4Aq4AMBSz6JnoesQoJ182RwBLxeCRMaxqfVsefln7tMXRuI5j3qdGHdWlwARJZKcr97Ya2xKqEslTn2SWgQIaRG6ZEO08+I6CZ8A+Fq/d9GTIVRMsJsRbIvhZmClJvjluvnreCkaYFo/q6k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=qocmwPew; 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="qocmwPew" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5C6351F0089B; Wed, 16 Sep 2026 10:33:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789554831; bh=SBbqHIjlwTzWE/9QBBjDjF/gPafRIE93aoSOCKnucQI=; h=From:To:Cc:Subject:Date:Reply-To; b=qocmwPewptibzaDUvae7BrIvBKt76lvp9yegFepenk2QGQen4qmWHnxFM8/RaS7Nc JpqH7iq87aDE7AXF29GJi5MFbSNCPP4ayE+no6Ay9HeszDKUEBStP7zTVVEuW9NqB5 PfbFZVr/ZYtlCIdVeW7cjrVVTre2J/UNt9nUVnoY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89819: drm/amd/display: validate plane degamma LUT size for private color prop Date: Wed, 16 Sep 2026 11:29:09 +0100 Message-ID: <2026091600-CVE-2026-89819-e5fd@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=3127; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=iZeEPfW0LEbEzq6Ra50QrKuMK4wDGIHIYoBaY4Hjk6Y=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmr8nPOP44OuNQ718Vh32r52WeDbs1iqpw75eC71uaLe 7Iic05ldsSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEZu1nmJ9rKrI2vW9hU2C2 cpqM7uWP09wDrzEsOOIxT/T4y7fKpZcuREuLSylXPp3yGwA= 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/amd/display: validate plane degamma LUT size for private color prop Unlike the CRTC degamma path, which is guarded by amdgpu_dm_verify_lut_sizes(), the per-plane degamma LUT size was never validated before use. __set_dm_plane_degamma() passed the user-supplied size straight into __is_lut_linear() and, for a non-linear LUT, into __set_input_tf() -> __drm_lut_to_dc_gamma(), the latter always iterating MAX_COLOR_LUT_ENTRIES entries regardless of the actual LUT size. A malformed AMD_PLANE_DEGAMMA_LUT blob (e.g. a single entry) could thus trigger a divide-by-zero in __is_lut_linear() or an out-of-bounds read in __drm_lut_to_dc_gamma(). Reject any plane degamma LUT whose size does not match MAX_COLOR_LUT_ENTRIES, mirroring the invariant the code already asserts a few lines below (and which the CRTC path enforces). The AMD_PLANE_DEGAMMA_LUT property is only exposed on builds with AMD_PRIVATE_COLOR defined. The Linux kernel CVE team has assigned CVE-2026-89819 to this issue. Affected and fixed versions =========================== Issue introduced in 6.8 with commit 980f8710075acaeb226a94cde6dda8ffad30123c and fixed in 6.12.110 with commit f6f04d8ae5725bcc893bdc62e3467efd97255c5b Issue introduced in 6.8 with commit 980f8710075acaeb226a94cde6dda8ffad30123c and fixed in 6.18.51 with commit 0b2615b8b54f58bbdf986dffb38cbc35214a5cc5 Issue introduced in 6.8 with commit 980f8710075acaeb226a94cde6dda8ffad30123c and fixed in 7.2.5 with commit b10cc09b329245c6d95f8fa3e7f068575e3e0e9f Issue introduced in 6.8 with commit 980f8710075acaeb226a94cde6dda8ffad30123c and fixed in 7.3-rc1 with commit e4c3ab59021e7c146a84b6671f0d530972bd58b4 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-89819 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/display/amdgpu_dm/amdgpu_dm_color.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/f6f04d8ae5725bcc893bdc62e3467efd97255c5b https://git.kernel.org/stable/c/0b2615b8b54f58bbdf986dffb38cbc35214a5cc5 https://git.kernel.org/stable/c/b10cc09b329245c6d95f8fa3e7f068575e3e0e9f https://git.kernel.org/stable/c/e4c3ab59021e7c146a84b6671f0d530972bd58b4