CVE-2026-90289drm/amd/display: Resize MST HDCP per-connector arrays to 32
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Resize MST HDCP per-connector arrays to 32 AMDGPU_DM_MAX_DISPLAY_INDEX is 31. It suggest a maximum number of 32 connectors. But the way it's used is like MAX_DISPLAY_COUNT. Hence we're off by one with DRM core, which supports a max of 32 connectors. Rename AMDGPU_DM_MAX_DISPLAY_INDEX to AMDGPU_DM_MAX_DISPLAY_COUNT to match its actual use, and increase the size to 32 to match the originally intended size.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 82986fd631fa04bcedaefe11a6b3767601cbe84f builds before 562d24ac214ba9530d88841088eb6adce5c537b5; 82986fd631fa04bcedaefe11a6b3767601cbe84f builds before 0fa116a17b69a28712cdf209318e345b676d7f6c; 82986fd631fa04bcedaefe11a6b3767601cbe84f builds before 261e0fe4e2c99f687114b64b10b98db964b475f4; 99c444d3c3c43db354b253d9bfac081073dcb484; d90f97cb3821c47bdf773dcf6cade143773ec764; from 5.15.128 before 5.16; from 6.1.47 before 6.2 | CNA record |
References
- https://git.kernel.org/stable/c/562d24ac214ba9530d88841088eb6adce5c537b5
- https://git.kernel.org/stable/c/0fa116a17b69a28712cdf209318e345b676d7f6c
- https://git.kernel.org/stable/c/261e0fe4e2c99f687114b64b10b98db964b475f4
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.