CVE-2026-46263·Kernel vulnerability
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)
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.19.4
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.18% — higher than 7% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-46263 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.18%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 6.19.4
Fixed in: 6.19.4
How to fix this CVE
Update your Linux kernel to version 6.19.4 or later to resolve this out-of-bounds memory access vulnerability in the AMD display driver. The vulnerability allows the stream encoder index to exceed array bounds during GPU initialization, potentially leading to memory corruption. Apply the patch immediately to systems running kernel versions 6.19 through 6.19.3.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check installed kernel version: uname -r — confirm if it falls within 6.19.0 to 6.19.3 range
- Verify AMD GPU is present: lspci | grep -i amd — if no AMD display adapter found, vulnerability surface is reduced
- Check dmesg for stream encoder errors: sudo dmesg | grep -i 'stream_encoder\|ENGINE_ID_DIG' — look for warnings or out-of-bounds access attempts during boot
- Verify kernel update applied: uname -r — confirm version is 6.19.4 or higher after applying patches
FAQ
What is CVE-2026-46263?
This vulnerability is an out-of-bounds array access in the Linux kernel's AMD display driver that occurs when an invalid stream encoder index is used to access the stream_enc_regs[] array, potentially causing memory corruption or system instability during GPU initialization.
Is CVE-2026-46263 being actively exploited?
No, this vulnerability is not listed on the CISA KEV catalog and has no known public exploits. However, it should still be patched as out-of-bounds memory access can lead to system crashes or information disclosure.
What versions of Kernel are affected by CVE-2026-46263?
Linux kernel versions 6.19.0 through 6.19.3 are affected. Kernel 6.19.4 and later versions contain the fix.
How do I check if my server is vulnerable to CVE-2026-46263?
Run 'uname -r' and compare the output to 6.19.0–6.19.3; if your version falls in this range and you have AMD GPU hardware, your system is vulnerable.
Does Defensia detect CVE-2026-46263?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-46263 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-46263. Free for 1 server.
Get started free