Skip to main content
VulnerabilityPublished Updated

CVE-2026-46263: Linux kernel · drm/amd/display: Fix out-of-bounds stream encoder index v3

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High · fixed in ca3808d560ad946ab6d089fd1f5bee04b952ead4 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:18 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in ca3808d560ad946ab6d089fd1f5bee04b952ead4, abde491143e4e12eecc41337910aace4e8d59603, 263e28add4f4472cfa95150d218955d1945aa413 +1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to ca3808d560ad946ab6d089fd1f5bee04b952ead4, abde491143e4e12eecc41337910aace4e8d59603, 263e28add4f4472cfa95150d218955d1945aa413 or 29f3824b08a98d41ecbbfd33580630d7607f962e.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 2728e9c7c84235d2d7bc1403174d071ffc82d6d2, < ca3808d560ad946ab6d089fd1f5bee04b952ead4
Fixed in
  • ca3808d560ad946ab6d089fd1f5bee04b952ead4
LinuxLinuxAffected
  • ≥ 2728e9c7c84235d2d7bc1403174d071ffc82d6d2, < abde491143e4e12eecc41337910aace4e8d59603
Fixed in
  • abde491143e4e12eecc41337910aace4e8d59603
LinuxLinuxAffected
  • ≥ 2728e9c7c84235d2d7bc1403174d071ffc82d6d2, < 263e28add4f4472cfa95150d218955d1945aa413
Fixed in
  • 263e28add4f4472cfa95150d218955d1945aa413
LinuxLinuxAffected
  • ≥ 2728e9c7c84235d2d7bc1403174d071ffc82d6d2, < 29f3824b08a98d41ecbbfd33580630d7607f962e
Fixed in
  • 29f3824b08a98d41ecbbfd33580630d7607f962e
LinuxLinuxAffected
  • =6.9
Fixed in–

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 <? 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)

References

Community reviews

Loading reviews…