dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53056

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.1.175 / 6.6.141 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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/

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In the Linux kernel's drm/msm/dpu driver, calling dev_pm_opp_set_rate(dev, 0) during DPU runtime suspend drops the MMCX voltage rail to MIN_SVS while the core clock frequency remains at its highest rate. This creates a mismatch where the lowered voltage rail cannot sustain the high clock frequency, potentially causing instability or system crashes when the DPU resumes.

MitigationApply the kernel patch that removes the dev_pm_opp_set_rate(dev, 0) call from dpu_runtime_suspend to ensure the correct voltage vote is maintained across suspend/resume cycles.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.9, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version against affected ranges
    Run 'uname -r' or 'cat /proc/version' and compare the kernel version to the affected ranges: >= 5.9 and < 6.1.175; >= 6.2 and < 6.6.141; >= 6.7 and < 6.12.91; >= 6.13 and < 6.18.33; >= 6.19 and < 7.0.10
    Affected if Kernel version falls within any of the listed affected ranges
  2. Verify drm/msm DPU driver is loaded
    Check for 'msm' or 'dpu' in loaded DRM modules: run 'lsmod | grep -i msm' or check /sys/class/drm for card* devices and inspect 'driver' attribute. Also check 'cat /sys/kernel/debug/dri/*/name' if debugfs is available
    Affected if The system uses the msm drm driver with DPU (Display Processing Unit) support
  3. Confirm runtime PM is enabled for DPU device
    Check runtime PM status: 'cat /sys/bus/platform/devices/*dpu*/power/control' or similar path under /sys/bus/platform/devices/ for dpu-related device entries. Look for 'auto' instead of 'on'
    Affected if Runtime PM control is set to 'auto', meaning the device can be runtime suspended/resumed
  4. Identify if MMCX voltage rail exists on the system
    Check for MMCX rail presence in kernel OPP (Operating Performance Points) data: look in /sys/class/devcoredump or examine 'cat /sys/kernel/debug/opp/opp_summary' if available, or check dmesg for 'MMCX' voltage rail messages during boot
    Affected if System uses MMCX voltage rail for DPU power management (typical on Qualcomm Snapdragon-based devices)
  5. Inspect dpu_runtime_suspend code for vulnerable call
    If kernel sources are available, grep the dpu driver: 'grep -n "dev_pm_opp_set_rate" drivers/gpu/drm/msm/disp/dpu1/*.c' or check if the function dpu_runtime_suspend contains a call to dev_pm_opp_set_rate(dev, 0)
    Affected if The dpu_runtime_suspend function contains 'dev_pm_opp_set_rate(dev, 0)' or similar zero-rate call that drops the voltage rail

You are affected if your kernel version is in the affected range AND the system uses the msm DPU driver with runtime PM enabled and the vulnerable code path exists on your hardware.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.175 / 6.6.141 / 6.12.91 or later
Fixed in 6.1.1756.6.1416.12.91
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch that removes the dev_pm_opp_set_rate(dev, 0) call from dpu_runtime_suspend to ensure the correct voltage vote is maintained across suspend/resume cycles.

Recommended fix High confidence

6.1.175+ (6.1.x), 6.6.141+ (6.6.x), 6.12.91+ (6.12.x), or 6.18.33+ (6.18.x) depending on branch

  1. Identify the currently running Linux kernel version using `uname -r`
  2. Determine which version branch you are on (e.g., 6.1.x, 6.6.x, 6.7.x, 6.12.x, 6.13.x, 6.18.x)
  3. Upgrade to the appropriate fixed kernel version: For 6.1.x branch, upgrade to >= 6.1.175; For 6.6.x branch, upgrade to >= 6.6.141; For 6.7-6.11.x branch, upgrade to >= 6.12.91; For 6.12.x branch, upgrade to >= 6.12.91; For 6.13-6.17.x branch, upgrade to >= 6.18.33; For 6.18.x branch, upgrade to >= 6.18.33
  4. Reboot the system to apply the new kernel
  5. Verify the fix is applied by checking the DPU driver code in `drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c` - the `dev_pm_opp_set_rate(dev, 0)` call should be removed from `dpu_runtime_suspend`
Caveat Kernel upgrades may introduce regressions; ensure compatibility with system hardware and other drivers before deploying in production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53056 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53056 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data