drm/msm/dpu: fix mismatch between power and frequency
Summary
| CVE | CVE-2026-53056 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-06-24 17:17:17 UTC |
| Updated | 2026-06-24 17:17:17 UTC |
| 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 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.
Patchwork: https://patchwork.freedesktop.org/patch/710077/ |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected b0530eb1191307e9038d75e5c83973a396137681 1181a7028d37e0b1e720a36125a03f5db97e3d27 git |
Not specified |
| CNA |
Linux |
Linux |
affected b0530eb1191307e9038d75e5c83973a396137681 9830999c9e065c1813ec5435bfe4eab98ee54a87 git |
Not specified |
| CNA |
Linux |
Linux |
affected b0530eb1191307e9038d75e5c83973a396137681 c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6 git |
Not specified |
| CNA |
Linux |
Linux |
affected b0530eb1191307e9038d75e5c83973a396137681 0f7dd5839cfabaf9c007fb718ec66e907a473c93 git |
Not specified |
| CNA |
Linux |
Linux |
affected b0530eb1191307e9038d75e5c83973a396137681 0ccf4f27b4652570b5de3de02a89a86435559de9 git |
Not specified |
| CNA |
Linux |
Linux |
affected b0530eb1191307e9038d75e5c83973a396137681 bc1dccc518cc5ab5140fba06c27e7188e0ed342b git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.9 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.9 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.175 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.141 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.91 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.33 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0.10 7.0.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/0ccf4f27b4652570b5de3de02a89a86435559de9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/bc1dccc518cc5ab5140fba06c27e7188e0ed342b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9830999c9e065c1813ec5435bfe4eab98ee54a87 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/1181a7028d37e0b1e720a36125a03f5db97e3d27 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0f7dd5839cfabaf9c007fb718ec66e907a473c93 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.