drm/amd/display: Check index msg_id before read or write
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c · < 59d99deb330af206a4541db0c4da8f73880fba03| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check index msg_id before read or write
[WHAT] msg_id is used as an array index and it cannot be a negative value, and therefore cannot be equal to MOD_HDCP_MESSAGE_ID_INVALID (-1).
[HOW] Check whether msg_id is valid before reading and setting.
This fixes 4 OVERRUN issues reported by Coverity.
From the CVE record · Linux
The Linux kernel’s AMD display code can use a negative msg_id as an array index when reading or writing HDCP messages. This can cause out-of-bounds access; the input does not establish whether an attacker can trigger it or what access or user interaction would be required.
Engineers running Linux kernels with the AMD display component should check their versions; affected versions were not provided.