GPU VulnDB

Database/NVIDIA / GPU stack

Linux kernel amdgpu: off-by-one in MST HDCP per-connector arrays sized 31 instead of 32

CVSS 7.8CVE-2026-90289NVIDIA / GPU stackcurated

Impact

amdgpu's display code sized its MST HDCP per-connector arrays from AMDGPU_DM_MAX_DISPLAY_INDEX (31) while using the value as a count, one short of the 32 connectors DRM core supports. The 32nd connector indexes one past the end of those arrays. Reaching this requires a display pipeline with that many connectors - typically a deep DisplayPort MST chain - so on datacenter AMD accelerators running headless, with display support unused or absent, the code path is not exercised. Worth tracking for AMD-GPU workstation and remote-desktop nodes inside a fleet rather than for MI-series compute nodes.

Who can reach it

Local, and gated on physical display topology: a user able to drive the DRM connector state on a machine with an AMD GPU and enough MST-attached connectors to reach index 31. No tenant-reachable path on a headless compute node.

What to do

Update to a stable kernel that renames the constant to AMDGPU_DM_MAX_DISPLAY_COUNT and sizes the arrays to 32 (backported across stable branches; see the linked commits), then reboot into it - amdgpu cannot be reloaded under active workloads, so this is a drain and reboot. On headless compute nodes it can reasonably wait for the next scheduled kernel maintenance window.

References

Related entries

All NVIDIA / GPU stack entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.