{"api_version":"1","generated_at":"2026-06-25T16:12:37+00:00","cve":"CVE-2026-53056","urls":{"html":"https://cve.report/CVE-2026-53056","api":"https://cve.report/api/cve/CVE-2026-53056.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53056","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53056"},"summary":{"title":"drm/msm/dpu: fix mismatch between power and frequency","description":"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 -> rpmhpd_sync_state\n  cpu1:                                     dpu_kms_hw_init\ntimeline 0 ------------------------------------------------> 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/","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-24 17:17:17","updated_at":"2026-06-24 17:17:17"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/0ccf4f27b4652570b5de3de02a89a86435559de9","name":"https://git.kernel.org/stable/c/0ccf4f27b4652570b5de3de02a89a86435559de9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/bc1dccc518cc5ab5140fba06c27e7188e0ed342b","name":"https://git.kernel.org/stable/c/bc1dccc518cc5ab5140fba06c27e7188e0ed342b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9830999c9e065c1813ec5435bfe4eab98ee54a87","name":"https://git.kernel.org/stable/c/9830999c9e065c1813ec5435bfe4eab98ee54a87","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6","name":"https://git.kernel.org/stable/c/c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1181a7028d37e0b1e720a36125a03f5db97e3d27","name":"https://git.kernel.org/stable/c/1181a7028d37e0b1e720a36125a03f5db97e3d27","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0f7dd5839cfabaf9c007fb718ec66e907a473c93","name":"https://git.kernel.org/stable/c/0f7dd5839cfabaf9c007fb718ec66e907a473c93","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53056","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53056","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b0530eb1191307e9038d75e5c83973a396137681 1181a7028d37e0b1e720a36125a03f5db97e3d27 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b0530eb1191307e9038d75e5c83973a396137681 9830999c9e065c1813ec5435bfe4eab98ee54a87 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b0530eb1191307e9038d75e5c83973a396137681 c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b0530eb1191307e9038d75e5c83973a396137681 0f7dd5839cfabaf9c007fb718ec66e907a473c93 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b0530eb1191307e9038d75e5c83973a396137681 0ccf4f27b4652570b5de3de02a89a86435559de9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b0530eb1191307e9038d75e5c83973a396137681 bc1dccc518cc5ab5140fba06c27e7188e0ed342b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.9","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.9 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1.175 6.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.141 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.91 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.33 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.10 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"1181a7028d37e0b1e720a36125a03f5db97e3d27","status":"affected","version":"b0530eb1191307e9038d75e5c83973a396137681","versionType":"git"},{"lessThan":"9830999c9e065c1813ec5435bfe4eab98ee54a87","status":"affected","version":"b0530eb1191307e9038d75e5c83973a396137681","versionType":"git"},{"lessThan":"c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6","status":"affected","version":"b0530eb1191307e9038d75e5c83973a396137681","versionType":"git"},{"lessThan":"0f7dd5839cfabaf9c007fb718ec66e907a473c93","status":"affected","version":"b0530eb1191307e9038d75e5c83973a396137681","versionType":"git"},{"lessThan":"0ccf4f27b4652570b5de3de02a89a86435559de9","status":"affected","version":"b0530eb1191307e9038d75e5c83973a396137681","versionType":"git"},{"lessThan":"bc1dccc518cc5ab5140fba06c27e7188e0ed342b","status":"affected","version":"b0530eb1191307e9038d75e5c83973a396137681","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.9"},{"lessThan":"5.9","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.1.*","status":"unaffected","version":"6.1.175","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.141","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.91","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.33","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.10","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.1.175","versionStartIncluding":"5.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.141","versionStartIncluding":"5.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.91","versionStartIncluding":"5.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.33","versionStartIncluding":"5.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.10","versionStartIncluding":"5.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"5.9","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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 -> rpmhpd_sync_state\n  cpu1:                                     dpu_kms_hw_init\ntimeline 0 ------------------------------------------------> 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/"}],"providerMetadata":{"dateUpdated":"2026-06-24T16:30:01.694Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/1181a7028d37e0b1e720a36125a03f5db97e3d27"},{"url":"https://git.kernel.org/stable/c/9830999c9e065c1813ec5435bfe4eab98ee54a87"},{"url":"https://git.kernel.org/stable/c/c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6"},{"url":"https://git.kernel.org/stable/c/0f7dd5839cfabaf9c007fb718ec66e907a473c93"},{"url":"https://git.kernel.org/stable/c/0ccf4f27b4652570b5de3de02a89a86435559de9"},{"url":"https://git.kernel.org/stable/c/bc1dccc518cc5ab5140fba06c27e7188e0ed342b"}],"title":"drm/msm/dpu: fix mismatch between power and frequency","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53056","datePublished":"2026-06-24T16:30:01.694Z","dateReserved":"2026-06-09T07:44:35.381Z","dateUpdated":"2026-06-24T16:30:01.694Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-24 17:17:17","lastModifiedDate":"2026-06-24 17:17:17","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53056","Ordinal":"1","Title":"drm/msm/dpu: fix mismatch between power and frequency","CVE":"CVE-2026-53056","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53056","Ordinal":"1","NoteData":"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 -> rpmhpd_sync_state\n  cpu1:                                     dpu_kms_hw_init\ntimeline 0 ------------------------------------------------> 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/","Type":"Description","Title":"drm/msm/dpu: fix mismatch between power and frequency"}]}}}