Linux vulnerability

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)

Published 10 Aug 2026Updated 3 Oct 20268 sources
CVSS 7.8

What happened

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)

Affected versions

Linux: 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f through before 92b7c6e3a1546c6db868b07e93fa6fb950d1d3a0 (git); 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f through before bf9c06c70f496f1ba4474caf95c69696c828340e (git); 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f through before 01ba5b36898d6258f584269537cc49e7b05cf7c6 (git); 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f through before ba8bf1dcbb44773e7a0fd13b42925c644e0d5e76 (git); 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f through before 5182e442e61397d446c36995b8f5676942d35b82 (git); 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f through before 679f23f0a3606afcef1ffabd72222f00a54ad9e3 (git); 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f through before 0676fecbb5242aa22c057e78326d6d6041db034c (git); 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f through before 9fa26b9eed6195bf840f39ac183b9a6237548755 (git); 4.15 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.