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 7D18438D40E for ; Wed, 3 Jun 2026 15:51:24 +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=1780501885; cv=none; b=n2JR9HbCMXp7/sDQyoDgOJLNspKivKOFdBWAWolaDaeTFJu1lRkC9RmHRSL5B9+bNbWIFPPwAhfG9w3aPWLxhkprEGTBBTHRg7Dy1AZ30+289yXlQBG413XaedbYa1mmwfcrpJsua5KzoJYggfc+Tdz+5+hGSzSAMJ0VMGfJ0DA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780501885; c=relaxed/simple; bh=SRG7KMrsS/SFyxsg+dkDujCIrn6UaUXKn3D2iHjNL9Q=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=UV7Trn1xW9swDKbarMP1diQHS9yE2wt1fWKLnc8/o3tBHuc5cbudKJ9pSnYeI6lWJRZsQAUT5Hm4TX9idAOiTkOqq++S3jZuC37M/Xt2ZbJONQF5BHpMU6lfx9mm/+L/XzFE7lX39a0UawrLqMUmH4XlnrxWCa+kixf3pQu5mlM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=i3HxGUcr; 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="i3HxGUcr" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8326E1F00893; Wed, 3 Jun 2026 15:51:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1780501884; bh=P0u519qvEqod/TnTQYW6ParOAk/eldDxFuVJ1Bei3oU=; h=From:To:Cc:Subject:Date:Reply-To; b=i3HxGUcr+Nlf1vUPNhu5O47NRkehrS+ulSCZ+9V0QMevCZqLRX+uw1udVEbTAdzgg WYX08gouf9TXBz++Z/Jtx/3m75bwrDiNWsi0BYAsBmVYskrzHlrJfvhHb4llJbI0si 11V3jJ15eoVSgF8XDQLBcUyekiRHJcTcdKiJtyog= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-46263: drm/amd/display: Fix out-of-bounds stream encoder index v3 Date: Wed, 3 Jun 2026 17:49:52 +0200 Message-ID: <2026060337-CVE-2026-46263-952d@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=4614; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=n0uzR9y6ohxugjIy+BGmfovWwrBNTM3QSHd7i+1UNGk=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkKvoL1S+/1/vo3aZPNq8cHsgptHrD6OnjdPHX5UdO+x lXha3fd74hlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJbJFlmCsQdyhhp8z/I2HX Pi86uWDzwh1RJwUZFtzYoloksvyCwp7A9Wb7Y6vkv/UEygIA 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: Fix out-of-bounds stream encoder index v3 eng_id can be negative and that stream_enc_regs[] can be indexed out of bounds. eng_id is used directly as an index into stream_enc_regs[], which has only 5 entries. When eng_id is 5 (ENGINE_ID_DIGF) or negative, this can access memory past the end of the array. Add a bounds check using ARRAY_SIZE() before using eng_id as an index. The unsigned cast also rejects negative values. This avoids out-of-bounds access. Fixes the below smatch error: dcn*_resource.c: stream_encoder_create() may index stream_enc_regs[eng_id] out of bounds (size 5). drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn351/dcn351_resource.c 1246 static struct stream_encoder *dcn35_stream_encoder_create( 1247 enum engine_id eng_id, 1248 struct dc_context *ctx) 1249 { ... 1255 1256 /* Mapping of VPG, AFMT, DME register blocks to DIO block instance */ 1257 if (eng_id <= ENGINE_ID_DIGF) { ENGINE_ID_DIGF is 5. should <= be dc_bios, 1283 eng_id, vpg, afmt, --> 1284 &stream_enc_regs[eng_id], ^^^^^^^^^^^^^^^^^^^^^^^ This stream_enc_regs[] array has 5 elements so we are one element beyond the end of the array. ... 1287 return &enc1->base; 1288 } v2: use explicit bounds check as suggested by Roman/Dan; avoid unsigned int cast v3: The compiler already knows how to compare the two values, so the cast (int) is not needed. (Roman) The Linux kernel CVE team has assigned CVE-2026-46263 to this issue. Affected and fixed versions =========================== Issue introduced in 6.9 with commit 2728e9c7c84235d2d7bc1403174d071ffc82d6d2 and fixed in 6.12.75 with commit 29f3824b08a98d41ecbbfd33580630d7607f962e Issue introduced in 6.9 with commit 2728e9c7c84235d2d7bc1403174d071ffc82d6d2 and fixed in 6.18.14 with commit 263e28add4f4472cfa95150d218955d1945aa413 Issue introduced in 6.9 with commit 2728e9c7c84235d2d7bc1403174d071ffc82d6d2 and fixed in 6.19.4 with commit ca3808d560ad946ab6d089fd1f5bee04b952ead4 Issue introduced in 6.9 with commit 2728e9c7c84235d2d7bc1403174d071ffc82d6d2 and fixed in 7.0 with commit abde491143e4e12eecc41337910aace4e8d59603 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-46263 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/dc/resource/dcn315/dcn315_resource.c drivers/gpu/drm/amd/display/dc/resource/dcn316/dcn316_resource.c drivers/gpu/drm/amd/display/dc/resource/dcn32/dcn32_resource.c drivers/gpu/drm/amd/display/dc/resource/dcn321/dcn321_resource.c drivers/gpu/drm/amd/display/dc/resource/dcn35/dcn35_resource.c drivers/gpu/drm/amd/display/dc/resource/dcn351/dcn351_resource.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/29f3824b08a98d41ecbbfd33580630d7607f962e https://git.kernel.org/stable/c/263e28add4f4472cfa95150d218955d1945aa413 https://git.kernel.org/stable/c/ca3808d560ad946ab6d089fd1f5bee04b952ead4 https://git.kernel.org/stable/c/abde491143e4e12eecc41337910aace4e8d59603