Skip to main content
EPSS 0.1%top 97%

In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: fix mismatch between power and frequency During DPU runtime… (CVE-2026-53056)

0
Medium
Published: 06/24/2026 (06/24/2026, 18:32:45 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel's drm/msm/dpu component caused a mismatch between power rail voltage and core clock frequency during DPU runtime suspend and resume. Specifically, dropping the MMCX rail voltage to MIN_SVS while the core clock remains at its highest frequency can cause system instability or crashes. The issue is fixed by removing the call that sets the clock rate to zero during suspend, ensuring proper power management on resume.

CVSS v3.1

Score 5.5medium

Attack Vector
Local
Attack Complexity
Low
Privileges Required
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

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/15/2026, 06:35:55 UTC

Technical Analysis

The vulnerability in the Linux kernel drm/msm/dpu subsystem involves a mismatch between power rail voltage and core clock frequency during DPU runtime suspend and resume. When dev_pm_opp_set_rate(dev, 0) is called during suspend, the MMCX power rail voltage drops to MIN_SVS, but the core clock frequency remains at its highest rate. Upon resume, only the clock is re-enabled without restoring the appropriate voltage level, causing the rail voltage to be insufficient for the clock frequency. This can lead to system instability or crashes. The fix removes the problematic call to dev_pm_opp_set_rate(dev, 0) from the dpu_runtime_suspend function to maintain correct voltage-frequency alignment.

Potential Impact

This vulnerability can cause system instability or crashes due to the power rail voltage being too low to sustain the core clock frequency after DPU runtime resume. There is no impact on confidentiality or integrity, but availability is affected (denial of service).

Mitigation Recommendations

A fix is available and has been applied in the Linux kernel by removing the call to dev_pm_opp_set_rate(dev, 0) from dpu_runtime_suspend. Users should update to the patched kernel version containing this fix. Patch status is confirmed by the vendor patchwork link. No additional mitigation is required beyond applying the official fix.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-6p48-fhqh-r738
Osv Schema Version
1.4.0
Aliases
["CVE-2026-53056"]
Database Specific Severity
MODERATE
Cvss Version
3.1

Threat ID: 6a5fcf481010f89cc2152cee

Added to database: 07/21/2026, 19:58:00 UTC

Last enriched: 09/15/2026, 06:35:55 UTC

Last updated: 09/15/2026, 06:35:55 UTC

Views: 21

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses