CVE-2026-53056: drm/msm/dpu: fix mismatch between power and frequency
drm/msm/dpu: fix mismatch between power and frequency
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.143.1-1 - Configuration
Remove the call to dev_pm_opp_set_rate(dev, 0) from dpu_runtime_suspend so that on runtime resume the clock can be re-enabled without the rail voltage being dropped to MIN_SVS while the core clock remains at its maximum frequency (MMCX rail/code mismatch).
Linux kernel DPU runtime suspend dev_pm_opp_set_rate(dev, 0) call presence = remove the call to dev_pm_opp_set_rate(dev, 0) from dpu_runtime_suspend - Compensating control
Apply the upstream fix referenced by Patchwork patch 710077 (drm/msm/dpu: fix mismatch between power and frequency / resolved vulnerability) to ensure the correct power-frequency vote is restored when the DPU resumes.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53056?
CVE-2026-53056 has a medium severity rating of 5.5.
How do I fix CVE-2026-53056?
To fix CVE-2026-53056, you should update to the latest version of the Linux kernel that addresses this vulnerability.
What systems are affected by CVE-2026-53056?
CVE-2026-53056 affects systems running the Linux kernel and specifically the drm/msm/dpu subsystem.
What is the impact of CVE-2026-53056?
The impact of CVE-2026-53056 includes potential instability in the power and frequency management during DPU runtime suspend.
When was CVE-2026-53056 published?
CVE-2026-53056 was published on June 24, 2026.