drm/amd/display: Fix out-of-bounds read in dp_get_eq_aux_rd_interval()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8e5100a575433cc185a2e224280fbd873b6692dd · < e8b4d37eba05141ee01794fc6b7f2da808cee83b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix out-of-bounds read in dp_get_eq_aux_rd_interval()
[Why & How] The aux_rd_interval array in struct dc_lttpr_caps is declared with MAX_REPEATER_CNT - 1 (7) elements, indexed 0..6. However, the offset parameter passed to dp_get_eq_aux_rd_interval() can be as large as MAX_REPEATER_CNT (8) when a sink reports 8 LTTPR repeaters via DPCD. This leads to an out-of-bounds read of aux_rd_interval[7] when offset is 8.
Fix this by growing aux_rd_interval to MAX_REPEATER_CNT elements to accommodate the full range of valid repeater counts defined by the DP spec.
(cherry picked from commit a55a458a8df37a65ffda5cf721d554a8f74f6b04)
From the CVE record · Linux
The Linux kernel’s AMD display driver can read past the end of an array in dp_get_eq_aux_rd_interval() when a DisplayPort sink reports eight LTTPR repeaters via DPCD. The input does not establish whether an attacker can control that report or specify an attack path, authentication requirement, or user interaction.
Engineers running Linux kernels with the AMD display driver should check their exposure; affected versions are not specified.