Cloudanix VulnDB

CVE-2026-98313

None

CVSS

—

EPSS

0.2%

Published

Oct 6, 2026

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A bug in the Linux display driver can cause certain Qualcomm-powered laptops to restart themselves whenever the screen connection fails to initialize.

Exploitation
Other
Attacker needs
Local User
Complexity
Moderate
Impact
Denial Of Service
Component
OS kernel
Class
Denial of service
Remediation
Patch
Effort
Medium
Patch risk
Low

What it actually does

Unconditional DP_STATE_CTRL_PUSH_IDLE write in msm_dp_display_atomic_disable when power_on is false causes timeout and TrustZone-forced reset of remote processors on Snapdragon platforms.

Why it matters to the business

Unexpected system resets on affected Qualcomm Snapdragon hardware during display link failures result in operational downtime and potential loss of unsaved work.

How an attack unfolds

An attacker with local access triggers a DP/eDP link training failure (for example by mode-setting or blanking an unsupported panel), then invokes the atomic disable path that performs the unguarded PUSH_IDLE write, leading to silent SoC reset.

How to fix it

Apply the upstream kernel patch that gates the PUSH_IDLE write behind the power_on flag. Rebuild and deploy a fixed kernel on all affected systems.

How to confirm the fix worked

Confirm the power_on guard exists before the DP_STATE_CTRL_PUSH_IDLE write in the driver source. Reproduce a link-training failure and verify the machine remains up without reset.

Typical attack path

  1. Trigger eDP/DP link training failure
  2. Invoke atomic disable (for example via fb blank or compositor teardown)
  3. Observe unconditional PUSH_IDLE write and timeout
  4. Trigger TrustZone remote-processor stop and machine reset

How to detect it

Search kernel logs for 'PUSH_IDLE pattern timedout' immediately followed by qcom_q6v5_pas fatal-error messages containing 'TZ force stop' or 'err fatal notification received from TZ'.

  • PUSH_IDLE pattern timedout
  • qcom_q6v5_pas.*fatal error received
  • sys_m_smsm.c.*TZ force stop

What your security team should do

  • Apply the fix to all systems running the vulnerable kernel on Snapdragon X2 Elite hardware
  • Increase monitoring of display training failures in dmesg
  • Test the patched kernel on representative hardware before broad rollout

The record

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/

Affected packages

Ecosystem Package Introduced Fixed