CVE-2026-93175: drm/amd/display: Fix dangling pointer in CRTC reset function
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix dangling pointer in CRTC reset function
amdgpudmcrtcresetstate() frees the old state before allocating a new one. If kzalloc() fails, the function returns without updating the state pointer, leaving a dangling pointer to already freed memory.
Fix this by allocating the new state first. On allocation failure, the old state remains untouched and the function safely returns.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
[adjust for movement around current amd-staging-drm-next]
Affected Software
Event History
Frequently Asked Questions
When can this issue be triggered?
It requires amdgpu_dm_crtc_reset_state() to attempt allocation of a new CRTC state and for kzalloc() to fail. In that failure case, the prior state had already been freed while the state pointer was not updated.
What is the immediate mitigation if an update cannot be applied?
No configuration workaround or operational mitigation is provided. The resolved change allocates the replacement state before freeing the old state, so applying the available stable fixes is the documented remediation.
How can I determine whether a kernel includes the fix?
Check whether the kernel contains either referenced stable commit: 32bd68edbc6cbcfac0e4033b64f0bcadbf0efef5 or 0aeed866cb938943908c3ba46422128e49d2d080. The fixed implementation preserves the old state when allocation of a new state fails.