drm/amd/display: set new_stream to NULL after release
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f · < 679f23f0a3606afcef1ffabd72222f00a54ad9e3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: set new_stream to NULL after release
In dm_update_crtc_state(), the skip_modeset path releases new_stream via dc_stream_release() but does not set the pointer to NULL.
If a later error (e.g., color management failure) triggers the fail label, the error path calls dc_stream_release() again on the same dangling pointer, causing a double release and potential use-after-free.
Fix this by setting new_stream to NULL after the initial release.
(cherry picked from commit 99f3af19073b3ddbfd96e789124cce12c4277b28)
From the CVE record · Linux
The Linux kernel’s AMD display driver can release the same stream twice in dm_update_crtc_state() if the skip_modeset path is followed by a later error. This can cause a potential use-after-free; the input does not establish how an attacker could trigger it or whether authentication or user interaction is required.
Engineers running Linux kernels with the AMD display driver should check their kernel version; affected versions are not specified.