{"id":"CVE-2026-53056","summary":"drm/msm/dpu: fix mismatch between power and frequency","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/dpu: fix mismatch between power and frequency\n\nDuring DPU runtime suspend, calling dev_pm_opp_set_rate(dev, 0) drops\nthe MMCX rail to MIN_SVS while the core clock frequency remains at its\noriginal (highest) rate. When runtime resume re-enables the clock, this\nmay result in a mismatch between the rail voltage and the clock rate.\n\nFor example, in the DPU bind path, the sequence could be:\n  cpu0: dev_sync_state -\u003e rpmhpd_sync_state\n  cpu1:                                     dpu_kms_hw_init\ntimeline 0 ------------------------------------------------\u003e t\n\nAfter rpmhpd_sync_state, the voltage performance is no longer guaranteed\nto stay at the highest level. During dpu_kms_hw_init, calling\ndev_pm_opp_set_rate(dev, 0) drops the voltage, causing the MMCX rail to\nfall to MIN_SVS while the core clock is still at its maximum frequency.\nWhen the power is re-enabled, only the clock is enabled, leading to a\nsituation where the MMCX rail is at MIN_SVS but the core clock is at its\nhighest rate. In this state, the rail cannot sustain the clock rate,\nwhich may cause instability or system crash.\n\nRemove the call to dev_pm_opp_set_rate(dev, 0) from dpu_runtime_suspend\nto ensure the correct vote is restored when DPU resumes.\n\nPatchwork: https://patchwork.freedesktop.org/patch/710077/","modified":"2026-07-22T18:22:28.224481684Z","published":"2026-06-24T16:30:01.694Z","related":["SUSE-SU-2026:3130-1","SUSE-SU-2026:3166-1"],"database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53056.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/0ccf4f27b4652570b5de3de02a89a86435559de9"},{"type":"WEB","url":"https://git.kernel.org/stable/c/0f7dd5839cfabaf9c007fb718ec66e907a473c93"},{"type":"WEB","url":"https://git.kernel.org/stable/c/1181a7028d37e0b1e720a36125a03f5db97e3d27"},{"type":"WEB","url":"https://git.kernel.org/stable/c/9830999c9e065c1813ec5435bfe4eab98ee54a87"},{"type":"WEB","url":"https://git.kernel.org/stable/c/bc1dccc518cc5ab5140fba06c27e7188e0ed342b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53056.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53056"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"b0530eb1191307e9038d75e5c83973a396137681"},{"fixed":"1181a7028d37e0b1e720a36125a03f5db97e3d27"},{"fixed":"9830999c9e065c1813ec5435bfe4eab98ee54a87"},{"fixed":"c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6"},{"fixed":"0f7dd5839cfabaf9c007fb718ec66e907a473c93"},{"fixed":"0ccf4f27b4652570b5de3de02a89a86435559de9"},{"fixed":"bc1dccc518cc5ab5140fba06c27e7188e0ed342b"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-53056.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.9.0"},{"fixed":"6.1.175"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.141"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.91"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.33"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.0.10"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-53056.json"}}],"schema_version":"1.7.5"}