drm/amd/display: Avoid HDCP over-read and corruption
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Avoid HDCP over-read and corruption
Instead of reading the desired 5 bytes of the actual target field, the code was reading 8. This could result in a corrupted value if the trailing 3 bytes were non-zero, so instead use an appropriately sized and zero-initialized bounce buffer, and read only 5 bytes before casting to u64.
From the CVE record · Linux
The Linux kernel’s AMD display HDCP code reads 8 bytes from a field that is only 5 bytes long. If the trailing 3 bytes are non-zero, this can corrupt the resulting value. The input does not specify how an attacker could trigger this or whether access or user interaction is required.
Engineers running Linux kernels with AMD display HDCP code should check their installations; affected versions are not specified.