CVE-2026-53056

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

drm/msm/dpu: fix mismatch between power and frequency

During DPU runtime suspend, calling dev_pm_opp_set_rate(dev, 0) drops

the MMCX rail to MIN_SVS while the core clock frequency remains at its

original (highest) rate. When runtime resume re-enables the clock, this

may result in a mismatch between the rail voltage and the clock rate.

For example, in the DPU bind path, the sequence could be:

cpu0: dev_sync_state -> rpmhpd_sync_state

cpu1: dpu_kms_hw_init

timeline 0 ------------------------------------------------> t

After rpmhpd_sync_state, the voltage performance is no longer guaranteed

to stay at the highest level. During dpu_kms_hw_init, calling

dev_pm_opp_set_rate(dev, 0) drops the voltage, causing the MMCX rail to

fall to MIN_SVS while the core clock is still at its maximum frequency.

When the power is re-enabled, only the clock is enabled, leading to a

situation where t

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References