drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8092aa3ab8f7b737a34b71f91492c676a843043a · < 7283b78ca07ce491984a63f6288f3f8de5bdcb22| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend
dc_state_create_copy() can return NULL on allocation failure. dm_suspend() only conditionally skips dm_gpureset_toggle_interrupts() and continues execution, returning success. dm_resume() then dereferences the NULL cached_dc_state in link_enc_cfg_copy() and the following dc_state->stream_count loop, crashing during GPU reset recovery.
Return -ENOMEM immediately if the copy fails, so the caller aborts suspend instead of leaving a NULL cached state for resume.
(cherry picked from commit 84b6d7932fdd2857795a257f9f258562a3cddcab)
From the CVE record · Linux
An allocation failure in the Linux kernel’s AMD display suspend path can leave a NULL cached state, which is dereferenced during GPU reset recovery and crashes the kernel. The input does not establish an attacker-triggered path or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with the affected AMD display code should check their versions; no affected versions are specified.