drm/amd/display: Add sanity checks for drm_edid_raw()
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: Add sanity checks for drm_edid_raw()
When EDID is retrieved via drm_edid_raw(), it doesn't guarantee to return proper EDID bytes the caller wants: it may be either NULL (that leads to an Oops) or with too long bytes over the fixed size raw_edid array (that may lead to memory corruption). The latter was reported actually when connected with a bad adapter.
Add sanity checks for drm_edid_raw() to address the above corner cases, and return EDID_BAD_INPUT accordingly.
(cherry picked from commit 648d3f4d209725d51900d6a3ed46b7b600140cdf)
From the CVE record · Linux
The Linux kernel's AMD display code does not adequately check data returned by drm_edid_raw(). A NULL result can cause a kernel Oops, while oversized data can corrupt memory; the latter was reported with a bad adapter. The input does not specify authentication requirements or other user interaction.
Engineers running Linux kernels with AMD display support should check their deployments; affected versions are not specified.