---
title: "CVE-2026-90289: CVE-2026-90289"
description: "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."
url: https://panop.io/threat-heartbeat/CVE-2026-90289/
---

# CVE-2026-90289 CVE-2026-90289

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 base score 7.8 /10

High

CISA KEV

Not listed

Public exploit

None known

EPSS

0.17% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-90289)

## Details

CVSS vector

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

Published

17 September 2026

Updated

15 October 2026

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-90289](https://nvd.nist.gov/vuln/detail/CVE-2026-90289)
- [https://git.kernel.org/stable/c/0fa116a17b69a28712cdf209318e345b676d7f6c](https://git.kernel.org/stable/c/0fa116a17b69a28712cdf209318e345b676d7f6c)
- [https://git.kernel.org/stable/c/261e0fe4e2c99f687114b64b10b98db964b475f4](https://git.kernel.org/stable/c/261e0fe4e2c99f687114b64b10b98db964b475f4)
- [https://git.kernel.org/stable/c/562d24ac214ba9530d88841088eb6adce5c537b5](https://git.kernel.org/stable/c/562d24ac214ba9530d88841088eb6adce5c537b5)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)