CVE-2026-53056drm/msm/dpu: fix mismatch between power and frequency
- 5.5MediumCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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/
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 94% of all CVEs (19 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected b0530eb1191307e9038d75e5c83973a396137681 – < 1181a7028d37e0b1e720a36125a03f5db97e3d27
- affected b0530eb1191307e9038d75e5c83973a396137681 – < 9830999c9e065c1813ec5435bfe4eab98ee54a87
- affected b0530eb1191307e9038d75e5c83973a396137681 – < c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6
- affected b0530eb1191307e9038d75e5c83973a396137681 – < 0f7dd5839cfabaf9c007fb718ec66e907a473c93
- affected b0530eb1191307e9038d75e5c83973a396137681 – < 0ccf4f27b4652570b5de3de02a89a86435559de9
- affected b0530eb1191307e9038d75e5c83973a396137681 – < bc1dccc518cc5ab5140fba06c27e7188e0ed342b
- affected 5.9
- unaffected < 5.9
- unaffected 6.1.175 – ≤ 6.1.*
- unaffected 6.6.141 – ≤ 6.6.*
- unaffected 6.12.91 – ≤ 6.12.*
- unaffected 6.18.33 – ≤ 6.18.*
- unaffected 7.0.10 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References6
- https://git.kernel.org/stable/c/1181a7028d37e0b1e720a36125a03f5db97e3d27 (opens in a new tab)
- https://git.kernel.org/stable/c/9830999c9e065c1813ec5435bfe4eab98ee54a87 (opens in a new tab)
- https://git.kernel.org/stable/c/c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6 (opens in a new tab)
- https://git.kernel.org/stable/c/0f7dd5839cfabaf9c007fb718ec66e907a473c93 (opens in a new tab)
- https://git.kernel.org/stable/c/0ccf4f27b4652570b5de3de02a89a86435559de9 (opens in a new tab)
- https://git.kernel.org/stable/c/bc1dccc518cc5ab5140fba06c27e7188e0ed342b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-38924 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-53056)Record last updated .