Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 4 weeks ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
drm/amd/display: set new_stream to NULL after release

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 products

Linux
  • ==4.15
  • <ba8bf1dcbb44773e7a0fd13b42925c644e0d5e76
  • =<6.6.*
  • =<*
  • <0676fecbb5242aa22c057e78326d6d6041db034c
  • <679f23f0a3606afcef1ffabd72222f00a54ad9e3
  • =<6.18.*
  • <4.15
  • =<6.12.*
  • =<7.1.*
  • <9fa26b9eed6195bf840f39ac183b9a6237548755
  • <5182e442e61397d446c36995b8f5676942d35b82