[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2026-31488":6},{"stargazers_count":4,"fetched_at":5},7,"2026-07-31T03:17:55.401Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":39},"DEBIAN-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 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:  \u003CTASK>  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_state_default_clear+0x8ee/0xf30  ? drm_mode_object_put.part.0+0xb1/0x130  __drm_atomic_state_free+0x15c/0x2d0  atomic_remove_fb+0x67e/0x980  Since there is no reliable way of figuring out whether a CRTC has unrelated mode changes pending at the time of DSC validation, remember the value of the mode_changed flag from before the point where a CRTC was marked as potentially affected by a change in DSC configuration. Reset the mode_changed flag to this earlier value instead in pre_validate_dsc().  (cherry picked from commit cc7c7121ae082b7b82891baa7280f1ff2608f22b)",null,[],[],[],[14],{"_key":15},"CVE-2026-31488",[],[],[],"2026-04-22T14:16:46.453Z","2026-07-05T20:00:16.069804797Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2026-31488",[27],"osv_debian",[29],"Advisory",[],[],[33],{"source":27,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":34,"cvss_v4_0":9},{"baseScore":35,"baseSeverity":9,"vectorString":36,"impactScore":37,"exploitabilityScore":38},7.8,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",9.8,4.6,[40,61],{"ecosystem":41,"name":42,"vendor":43,"product":42,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":42,"source":9,"versions":45},"Debian","linux","debian","deb",[46,50,51,55,58],{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":9,"version_end_type":9,"fixed_in":9},"all",true,"ecosystem",{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":9,"version_end_type":9,"fixed_in":9},{"version":52,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":53,"version_end_type":54,"fixed_in":9},"lt6_1_176_1","6.1.176-1","excluding",{"version":56,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":57,"version_end_type":54,"fixed_in":9},"lt6_12_85_1","6.12.85-1",{"version":59,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":60,"version_end_type":54,"fixed_in":9},"lt6_19_11_1","6.19.11-1",{"ecosystem":41,"name":62,"vendor":43,"product":62,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":62,"source":9,"versions":63},"linux-6.1",[64],{"version":65,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":66,"version_end_type":54,"fixed_in":9},"lt6_1_176_1~deb11u1","6.1.176-1~deb11u1"]