KernelScan.io

HIGH

drm/amd StreamEncoder OOB

CVE-2026-46263

CVSS 7.8 / 10.0 NVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

KernelScan AI7.8HIGH

01

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 <? Unrelated but, ugh, why is Smatch saying that "eng_id" can be negative? end_id is type signed long, but there are checks in the caller which prevent it from being negative. 1258 vpg_inst = eng_id; 1259 afmt_inst = eng_id; 1260 } else 1261 return NULL; 1262 ... 1281 1282 dcn35_dio_stream_encoder_construct(enc1, ctx, ctx->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)

02

Engine v0.2.0

Risk summary

Local attackers with low privileges can trigger out-of-bounds memory access in AMD GPU display driver functions. This can lead to kernel memory corruption, information disclosure, or system crashes when creating stream encoders with invalid engine IDs.

Affecteddrivers/gpu/drm/amd/display/dc/resource/dcn*/dcn*_resource.c (AMD GPU display driver)

Vulnerability analysis

The vulnerability occurs in multiple AMD display controller (DCN) resource files where the eng_id parameter is used directly as an array index into stream_enc_regs[] without proper bounds checking. The array has only 5 elements (indices 0-4), but eng_id can be 5 (ENGINE_ID_DIGF) or negative values, causing out-of-bounds access. The original code only checked if eng_id <= ENGINE_ID_DIGF (5), allowing index 5 to pass through. The fix adds explicit bounds checking using ARRAY_SIZE() and rejects negative values before using eng_id as an array index. This affects AMD GPU hardware initialization and display stream encoder creation, requiring local access to GPU device nodes.

03

BranchFixed inPatch commit
6.126.12.7529f3824b08a9
6.186.18.14263e28add4f4
6.196.19.4ca3808d560ad
mainline7.0abde491143e4