CVE-2026-53056

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/msm/dpu: fix mismatch between power and frequency<br /> <br /> During DPU runtime suspend, calling dev_pm_opp_set_rate(dev, 0) drops<br /> the MMCX rail to MIN_SVS while the core clock frequency remains at its<br /> original (highest) rate. When runtime resume re-enables the clock, this<br /> may result in a mismatch between the rail voltage and the clock rate.<br /> <br /> For example, in the DPU bind path, the sequence could be:<br /> cpu0: dev_sync_state -&gt; rpmhpd_sync_state<br /> cpu1: dpu_kms_hw_init<br /> timeline 0 ------------------------------------------------&gt; t<br /> <br /> After rpmhpd_sync_state, the voltage performance is no longer guaranteed<br /> to stay at the highest level. During dpu_kms_hw_init, calling<br /> dev_pm_opp_set_rate(dev, 0) drops the voltage, causing the MMCX rail to<br /> fall to MIN_SVS while the core clock is still at its maximum frequency.<br /> When the power is re-enabled, only the clock is enabled, leading to a<br /> situation where the MMCX rail is at MIN_SVS but the core clock is at its<br /> highest rate. In this state, the rail cannot sustain the clock rate,<br /> which may cause instability or system crash.<br /> <br /> Remove the call to dev_pm_opp_set_rate(dev, 0) from dpu_runtime_suspend<br /> to ensure the correct vote is restored when DPU resumes.<br /> <br /> Patchwork: https://patchwork.freedesktop.org/patch/710077/