CVE-2026-98313 (GCVE-0-2026-98313)

Vulnerability from cvelistv5 – Published: 2026-10-06 08:46 – Updated: 2026-10-06 08:46
VLAI
Title
drm/msm/dp: skip PUSH_IDLE when the link was never enabled
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dp: skip PUSH_IDLE when the link was never enabled msm_dp_display_atomic_enable() returns early when link training fails, leaving ->power_on false and the main link down. msm_dp_display_atomic_disable() nevertheless writes DP_STATE_CTRL_PUSH_IDLE and waits for an idle-pattern completion that cannot arrive, so every failed enable is followed by "PUSH_IDLE pattern timedout". Every other step of the teardown is already gated on that flag: msm_dp_display_disable(), called from .atomic_post_disable(), returns early on !power_on. The PUSH_IDLE write is the only one that is not, so the controller's runtime-PM reference is then dropped without the link having been taken down. On glymur (Snapdragon X2 Elite) the consequence is not a warning. The SoC does not survive it: TrustZone force-stops the SOCCP and ADSP remote processors and the machine resets silently about 50 ms later, with no oops and no panic. On an ASUS Zenbook A16 (UX3607OA), whose eDP panel does not currently train, this reproduces without any compositor or GPU involvement: # eDP enable has already failed with "Failed link training (rc=-104)" echo 1 > /sys/class/graphics/fb0/blank [535.645455] === marker === [535.694833] qcom_q6v5_pas d00000.remoteproc: fatal error received: \ sys_m_smsm.c:512:TZ force stop [535.694875] remoteproc remoteproc0: crash detected in soccp: type fatal error [535.728857] qcom_q6v5_pas 6800000.remoteproc: fatal error received: \ sys_m_smsm.c:783:err fatal notification received from TZ <SoC reset> Gate the PUSH_IDLE write on ->power_on so the disable path is consistent with the rest of the teardown. With this applied the same sequence is harmless and the machine stays up; without it, it resets every time. The unconditional write dates back to the original DP driver (c943b4948b58 ("drm/msm/dp: add displayPort driver support")), but the surrounding code has been restructured several times since, so no Fixes: tag is offered. Note that the eDP link-training failure that exposes this on the A16 is a separate problem in the glymur eDP PHY and is reported separately; this change is about not damaging the machine when training fails, for whatever reason. Tested on ASUS Zenbook A16 (UX3607OA), Snapdragon X2 Elite Extreme, on linux-next next-20260803 and next-20260807. The machine has since been running next-20260807 with this patch as its daily driver. Patchwork: https://patchwork.freedesktop.org/patch/745167/
Severity
No CVSS data available.
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 6666 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < dc57147549a10c99766144cde265645287718ff7 (git)
Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 5e97d117b79c3ce89542369ef697be64850de8ad (git)
Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < e249a6e2a130c08bb4d8b0a55cbe29754307e5c9 (git)
Affected: 0 , < 6.18.54 (semver)
Affected: 0 , < 7.2.8 (semver)
guessed Create a notification for this product.
Linux Linux Unaffected: 6.18.54 , ≤ 6.18.* (semver)
Unaffected: 7.2.8 , ≤ 7.2.* (semver)
Unaffected: 7.3-rc4 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/msm/dp/dp_display.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "dc57147549a10c99766144cde265645287718ff7",
              "status": "affected",
              "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
              "versionType": "git"
            },
            {
              "lessThan": "5e97d117b79c3ce89542369ef697be64850de8ad",
              "status": "affected",
              "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
              "versionType": "git"
            },
            {
              "lessThan": "e249a6e2a130c08bb4d8b0a55cbe29754307e5c9",
              "status": "affected",
              "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
              "versionType": "git"
            },
            {
              "lessThan": "6.18.54",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThan": "7.2.8",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/msm/dp/dp_display.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.54",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.8",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc4",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.54",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc4",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/dp: skip PUSH_IDLE when the link was never enabled\n\nmsm_dp_display_atomic_enable() returns early when link training fails,\nleaving -\u003epower_on false and the main link down.\nmsm_dp_display_atomic_disable() nevertheless writes DP_STATE_CTRL_PUSH_IDLE\nand waits for an idle-pattern completion that cannot arrive, so every failed\nenable is followed by \"PUSH_IDLE pattern timedout\".\n\nEvery other step of the teardown is already gated on that flag:\nmsm_dp_display_disable(), called from .atomic_post_disable(), returns early\non !power_on. The PUSH_IDLE write is the only one that is not, so the\ncontroller\u0027s runtime-PM reference is then dropped without the link having\nbeen taken down.\n\nOn glymur (Snapdragon X2 Elite) the consequence is not a warning. The SoC\ndoes not survive it: TrustZone force-stops the SOCCP and ADSP remote\nprocessors and the machine resets silently about 50 ms later, with no oops\nand no panic. On an ASUS Zenbook A16 (UX3607OA), whose eDP panel does not\ncurrently train, this reproduces without any compositor or GPU involvement:\n\n  # eDP enable has already failed with \"Failed link training (rc=-104)\"\n  echo 1 \u003e /sys/class/graphics/fb0/blank\n\n  [535.645455] === marker ===\n  [535.694833] qcom_q6v5_pas d00000.remoteproc: fatal error received: \\\n                 sys_m_smsm.c:512:TZ force stop\n  [535.694875] remoteproc remoteproc0: crash detected in soccp: type fatal error\n  [535.728857] qcom_q6v5_pas 6800000.remoteproc: fatal error received: \\\n                 sys_m_smsm.c:783:err fatal notification received from TZ\n  \u003cSoC reset\u003e\n\nGate the PUSH_IDLE write on -\u003epower_on so the disable path is consistent\nwith the rest of the teardown. With this applied the same sequence is\nharmless and the machine stays up; without it, it resets every time.\n\nThe unconditional write dates back to the original DP driver\n(c943b4948b58 (\"drm/msm/dp: add displayPort driver support\")), but the\nsurrounding code has been restructured several times since, so no Fixes:\ntag is offered.\n\nNote that the eDP link-training failure that exposes this on the A16 is a\nseparate problem in the glymur eDP PHY and is reported separately; this\nchange is about not damaging the machine when training fails, for whatever\nreason.\n\nTested on ASUS Zenbook A16 (UX3607OA), Snapdragon X2 Elite Extreme, on\nlinux-next next-20260803 and next-20260807. The machine has since been\nrunning next-20260807 with this patch as its daily driver.\n\nPatchwork: https://patchwork.freedesktop.org/patch/745167/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-06T08:46:09.174Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/dc57147549a10c99766144cde265645287718ff7"
        },
        {
          "url": "https://git.kernel.org/stable/c/5e97d117b79c3ce89542369ef697be64850de8ad"
        },
        {
          "url": "https://git.kernel.org/stable/c/e249a6e2a130c08bb4d8b0a55cbe29754307e5c9"
        }
      ],
      "title": "drm/msm/dp: skip PUSH_IDLE when the link was never enabled",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-98313",
    "datePublished": "2026-10-06T08:46:09.174Z",
    "dateReserved": "2026-09-25T10:25:14.339Z",
    "dateUpdated": "2026-10-06T08:46:09.174Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-98313",
      "date": "2026-10-16",
      "epss": "0.00173",
      "percentile": "0.06338"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "drivers/gpu/drm/msm/dp/dp_display.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "dc57147549a10c99766144cde265645287718ff7",
                    "status": "affected",
                    "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "5e97d117b79c3ce89542369ef697be64850de8ad",
                    "status": "affected",
                    "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "e249a6e2a130c08bb4d8b0a55cbe29754307e5c9",
                    "status": "affected",
                    "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "6.18.54",
                    "status": "affected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "7.2.8",
                    "status": "affected",
                    "version": "0",
                    "versionType": "semver"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "drivers/gpu/drm/msm/dp/dp_display.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThanOrEqual": "6.18.*",
                    "status": "unaffected",
                    "version": "6.18.54",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.2.*",
                    "status": "unaffected",
                    "version": "7.2.8",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "7.3-rc4",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/dp: skip PUSH_IDLE when the link was never enabled\n\nmsm_dp_display_atomic_enable() returns early when link training fails,\nleaving -\u003epower_on false and the main link down.\nmsm_dp_display_atomic_disable() nevertheless writes DP_STATE_CTRL_PUSH_IDLE\nand waits for an idle-pattern completion that cannot arrive, so every failed\nenable is followed by \"PUSH_IDLE pattern timedout\".\n\nEvery other step of the teardown is already gated on that flag:\nmsm_dp_display_disable(), called from .atomic_post_disable(), returns early\non !power_on. The PUSH_IDLE write is the only one that is not, so the\ncontroller\u0027s runtime-PM reference is then dropped without the link having\nbeen taken down.\n\nOn glymur (Snapdragon X2 Elite) the consequence is not a warning. The SoC\ndoes not survive it: TrustZone force-stops the SOCCP and ADSP remote\nprocessors and the machine resets silently about 50 ms later, with no oops\nand no panic. On an ASUS Zenbook A16 (UX3607OA), whose eDP panel does not\ncurrently train, this reproduces without any compositor or GPU involvement:\n\n  # eDP enable has already failed with \"Failed link training (rc=-104)\"\n  echo 1 \u003e /sys/class/graphics/fb0/blank\n\n  [535.645455] === marker ===\n  [535.694833] qcom_q6v5_pas d00000.remoteproc: fatal error received: \\\n                 sys_m_smsm.c:512:TZ force stop\n  [535.694875] remoteproc remoteproc0: crash detected in soccp: type fatal error\n  [535.728857] qcom_q6v5_pas 6800000.remoteproc: fatal error received: \\\n                 sys_m_smsm.c:783:err fatal notification received from TZ\n  \u003cSoC reset\u003e\n\nGate the PUSH_IDLE write on -\u003epower_on so the disable path is consistent\nwith the rest of the teardown. With this applied the same sequence is\nharmless and the machine stays up; without it, it resets every time.\n\nThe unconditional write dates back to the original DP driver\n(c943b4948b58 (\"drm/msm/dp: add displayPort driver support\")), but the\nsurrounding code has been restructured several times since, so no Fixes:\ntag is offered.\n\nNote that the eDP link-training failure that exposes this on the A16 is a\nseparate problem in the glymur eDP PHY and is reported separately; this\nchange is about not damaging the machine when training fails, for whatever\nreason.\n\nTested on ASUS Zenbook A16 (UX3607OA), Snapdragon X2 Elite Extreme, on\nlinux-next next-20260803 and next-20260807. The machine has since been\nrunning next-20260807 with this patch as its daily driver.\n\nPatchwork: https://patchwork.freedesktop.org/patch/745167/"
          }
        ],
        "id": "CVE-2026-98313",
        "lastModified": "2026-10-06T09:18:22.887",
        "metrics": {},
        "published": "2026-10-06T09:18:22.887",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/5e97d117b79c3ce89542369ef697be64850de8ad"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/dc57147549a10c99766144cde265645287718ff7"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/e249a6e2a130c08bb4d8b0a55cbe29754307e5c9"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-10-09T17:54:34+00:00",
      "cve": "CVE-2026-98313",
      "id": "CVE-2026-98313",
      "initial_release_date": "2026-10-06T00:00:00+00:00",
      "product_status:known_not_affected": "277",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: drm/msm/dp: skip PUSH_IDLE when the link was never enabled",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98313.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-10-07T16:27:59Z",
      "cve": "CVE-2026-98313",
      "id": "CVE-2026-98313",
      "initial_release_date": "2026-10-07T16:27:59Z",
      "product_status:known_affected": "12",
      "product_status:known_not_affected": "335",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-98313",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-98313.json",
      "version": "2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.