Skip to content
Heist/ feed
Back to feed
HighFix available

drm/amd/display: Do not skip unrelated mode changes in DSC validation

Type: advisorySources: OSV

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/

Products
Kernel
Affected versions
Not specified
Fixed versions
6.1.175, 6.12.80, 6.18.21, 6.19.11, 6.6.140
CVEs
CVE-2026-31488
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 14:27 UTC · Revision 1

Source evidence

drm/amd/display: Do not skip unrelated mode changes in DSC validation

core-osv · Original source

Published 22 Apr 2026, 13:54 UTC

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/

osv:CVE-2026-31488

Kernel

Fixed versions: 6.1.175, 6.6.140, 6.12.80, 6.18.21, 6.19.11

Complete source record
{
  "id": "89d45f28ebcbd06ac7afeaba90ba5e189ce9b725965d3def9155b69f7dd068ae",
  "url": "https://osv.dev/vulnerability/CVE-2026-31488",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "drm/amd/display: Do not skip unrelated mode changes in DSC validation",
    "summary": "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/",
    "evidence": "osv:CVE-2026-31488",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.1.175",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.140",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.80",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.21",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.19.11",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2026-31488",
      "aliases": [
        "CVE-2026-31488"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "17ce8a6907f77b7ac97ddaa071d8a1f6e06ce85b"
                },
                {
                  "fixed": "da1d0ed31e9802fd99384f43cc63678a5a11cb41"
                },
                {
                  "fixed": "21159d8b335a6b9f44cbb506733013a902ae2da4"
                },
                {
                  "fixed": "10862e344b4d6434642a48c87d765813fc0b0ba7"
                },
                {
                  "fixed": "8a5edc97fd9c6415ff2eff872748439a97e3c3d8"
                },
                {
                  "fixed": "111208b5b7ebcdadb3f922cc52d8425f0fa91b33"
                },
                {
                  "fixed": "aed3d041ab061ec8a64f50a3edda0f4db7280025"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31488.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.18.0"
                },
                {
                  "fixed": "6.1.175"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.140"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.80"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.21"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "6.19.11"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31488.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:29.404679005Z",
      "provider": "osv",
      "references": [
        "https://cert-portal.siemens.com/productcert/html/ssa-784472.html",
        "https://git.kernel.org/stable/c/10862e344b4d6434642a48c87d765813fc0b0ba7",
        "https://git.kernel.org/stable/c/111208b5b7ebcdadb3f922cc52d8425f0fa91b33",
        "https://git.kernel.org/stable/c/21159d8b335a6b9f44cbb506733013a902ae2da4",
        "https://git.kernel.org/stable/c/8a5edc97fd9c6415ff2eff872748439a97e3c3d8",
        "https://git.kernel.org/stable/c/aed3d041ab061ec8a64f50a3edda0f4db7280025",
        "https://git.kernel.org/stable/c/da1d0ed31e9802fd99384f43cc63678a5a11cb41",
        "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-31488.json",
        "https://access.redhat.com/errata/RHSA-2026:27353",
        "https://access.redhat.com/errata/RHSA-2026:27354",
        "https://access.redhat.com/errata/RHSA-2026:30848",
        "https://access.redhat.com/errata/RHSA-2026:43231",
        "https://access.redhat.com/errata/RHSA-2026:44385",
        "https://access.redhat.com/errata/RHSA-2026:47632",
        "https://access.redhat.com/errata/RHSA-2026:47739",
        "https://access.redhat.com/errata/RHSA-2026:47869",
        "https://access.redhat.com/errata/RHSA-2026:53330",
        "https://access.redhat.com/errata/RHSA-2026:55445",
        "https://access.redhat.com/security/cve/CVE-2026-31488",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31488.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-31488",
        "https://bugzilla.redhat.com/show_bug.cgi?id=2460619",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31488.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-31488",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 496374,
  "published_at": "2026-04-22T13:54:12.963+00:00"
}