cbcvebase.
CVE-2026-31488
published 2026-04-22

CVE-2026-31488: In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Do not skip unrelated mode changes in DSC validation Starting with commit…

PriorityP341high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.14%
3.8th percentile
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Do not skip unrelated mode changes in DSC validation Starting with commit 17ce8a6907f7 ("drm/amd/display: Add dsc pre-validation in atomic check"), amdgpu resets the CRTC state mode_changed flag to false when recomputing the DSC configuration results in no timing change for a particular stream. However, this is incorrect in scenarios where a change in MST/DSC configuration happens in the same KMS commit as another (unrelated) mode change. For example, the integrated panel of a laptop may be configured differently (e.g., HDR enabled/disabled) depending on whether external screens are attached. In this case, plugging in external DP-MST screens may result in the mode_changed flag being dropped incorrectly for the integrated panel if its DSC configuration did not change during precomputation in pre_validate_dsc(). At this point, however, dm_update_crtc_state() has already created new streams for CRTCs with DSC-independent mode changes. In turn, amdgpu_dm_commit_streams() will never release the old stream, resulting in a memory leak. amdgpu_dm_atomic_commit_tail() will never acquire a reference to the new stream either, which manifests as a use-after-free when the stream gets disabled later on: BUG: KASAN: use-after-free in dc_stream_release+0x25/0x90 [amdgpu] Write of size 4 at addr ffff88813d836524 by task kworker/9:9/29977 Workqueue: events drm_mode_rmfb_work_fn Call Trace: dump_stack_lvl+0x6e/0xa0 print_address_description.constprop.0+0x88/0x320 ? dc_stream_release+0x25/0x90 [amdgpu] print_report+0xfc/0x1ff ? srso_alias_return_thunk+0x5/0xfbef5 ? __virt_addr_valid+0x225/0x4e0 ? dc_stream_release+0x25/0x90 [amdgpu] kasan_report+0xe1/0x180 ? dc_stream_release+0x25/0x90 [amdgpu] kasan_check_range+0x125/0x200 dc_stream_release+0x25/0x90 [amdgpu] dc_state_destruct+0x14d/0x5c0 [amdgpu] dc_state_release.part.0+0x4e/0x130 [amdgpu] dm_atomic_destroy_state+0x3f/0x70 [amdgpu] drm_atomic_

Affected

41 ranges· showing 25
VendorProductVersion rangeFixed in
linuxlinux
linuxlinux>= 17ce8a6907f77b7ac97ddaa071d8a1f6e06ce85b < da1d0ed31e9802fd99384f43cc63678a5a11cb41da1d0ed31e9802fd99384f43cc63678a5a11cb41
linuxlinux>= 17ce8a6907f77b7ac97ddaa071d8a1f6e06ce85b < 21159d8b335a6b9f44cbb506733013a902ae2da421159d8b335a6b9f44cbb506733013a902ae2da4
linuxlinux>= 17ce8a6907f77b7ac97ddaa071d8a1f6e06ce85b < 10862e344b4d6434642a48c87d765813fc0b0ba710862e344b4d6434642a48c87d765813fc0b0ba7
linuxlinux>= 17ce8a6907f77b7ac97ddaa071d8a1f6e06ce85b < 8a5edc97fd9c6415ff2eff872748439a97e3c3d88a5edc97fd9c6415ff2eff872748439a97e3c3d8
linuxlinux>= 17ce8a6907f77b7ac97ddaa071d8a1f6e06ce85b < 111208b5b7ebcdadb3f922cc52d8425f0fa91b33111208b5b7ebcdadb3f922cc52d8425f0fa91b33
linuxlinux>= 17ce8a6907f77b7ac97ddaa071d8a1f6e06ce85b < aed3d041ab061ec8a64f50a3edda0f4db7280025aed3d041ab061ec8a64f50a3edda0f4db7280025
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 5.18.1 < 6.12.806.12.80
linuxlinux_kernel>= 6.13 < 6.18.216.18.21
linuxlinux_kernel>= 6.19 < 6.19.116.19.11
ubuntulinux
ubuntulinux-aws
ubuntulinux-azure
ubuntulinux-azure-6.8
ubuntulinux-azure-fde
ubuntulinux-azure-fde-6.8
ubuntulinux-azure-fips

CVSS provenance

nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vendor_ubuntu2.0LOW
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.