PT-2026-51950 · Linux · Linux
Published
2026-06-24
·
Updated
2026-06-24
·
CVE-2026-53056
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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 the MMCX rail is at MIN SVS but the core clock is at its
highest rate. In this state, the rail cannot sustain the clock rate,
which may cause instability or system crash.
Remove the call to dev pm opp set rate(dev, 0) from dpu runtime suspend
to ensure the correct vote is restored when DPU resumes.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux