drm/amd/display: Add null pointer check for get_first_active_display()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2deade5ede56581722c0d7672f28b09548dc0fc4 · < c3e9826a22027a21d998d3e64882fa377b613006| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Add null pointer check for get_first_active_display()
The function mod_hdcp_hdcp1_enable_encryption() calls the function get_first_active_display(), but does not check its return value. The return value is a null pointer if the display list is empty. This will lead to a null pointer dereference in mod_hdcp_hdcp2_enable_encryption().
Add a null pointer check for get_first_active_display() and return MOD_HDCP_STATUS_DISPLAY_NOT_FOUND if the function return null.
From the CVE record · Linux
The Linux kernel's AMD display HDCP code does not check whether get_first_active_display() returns null. When the display list is empty, this can cause a null pointer dereference. The input does not establish an attacker path or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with AMD display HDCP code should check their exposure; affected versions are not specified.