CVE-2026-53056
Received Received - Intake
DPU Runtime Suspend Power-Frequency Mismatch in Linux Kernel

Publication date: 2026-06-24

Last updated on: 2026-06-24

Assigner: kernel.org

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/
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-24
Last Modified
2026-06-24
Generated
2026-06-25
AI Q&A
2026-06-24
EPSS Evaluated
N/A
NVD
CVE-2026-53056
EUVD
EUVD-2026-38924
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the Linux kernel's Direct Rendering Manager (DRM) for the MSM Display Processing Unit (DPU). It involves a mismatch between power supply voltage and core clock frequency during the DPU's runtime suspend and resume processes.

Specifically, during runtime suspend, a function call drops the MMCX power rail voltage to a minimum level (MIN_SVS) while the core clock frequency remains at its highest rate. When the system resumes, the clock is re-enabled but the voltage rail remains at the low level, causing a mismatch.

This mismatch means the power rail cannot sustain the high clock frequency, which may lead to system instability or crashes.

The fix involves removing the call that sets the clock rate to zero during suspend, ensuring the voltage and clock frequency remain properly synchronized.

Impact Analysis

This vulnerability can cause system instability or crashes due to the mismatch between the power rail voltage and the core clock frequency in the DPU component of the Linux kernel.

If exploited or triggered, it could lead to unexpected system behavior, potentially causing downtime or data loss depending on the system's role.

Mitigation Strategies

The vulnerability is caused by a mismatch between the power rail voltage and the core clock frequency during DPU runtime suspend and resume in the Linux kernel.

To mitigate this vulnerability, the fix involves removing the call to dev_pm_opp_set_rate(dev, 0) from the dpu_runtime_suspend function. This ensures that the correct voltage vote is restored when the DPU resumes, preventing the MMCX rail from dropping to MIN_SVS while the core clock remains at its highest rate.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53056. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart