Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53056: drm/msm/dpu: fix mismatch between power and frequency

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0ccf4f27b4652570b5de3de02a89a86435559de9, 0f7dd5839cfabaf9c007fb718ec66e907a473c93, 1181a7028d37e0b1e720a36125a03f5db97e3d27; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0ccf4f27b4652570b5de3de02a89a86435559de9, 0f7dd5839cfabaf9c007fb718ec66e907a473c93, 1181a7028d37e0b1e720a36125a03f5db97e3d27; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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/

Published
Jun 24, 2026
Updated
Jul 21, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53056

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.9affected
    • b0530eb1191307e9038d75e5c83973a396137681 and later · before 1181a7028d37e0b1e720a36125a03f5db97e3d27affected · git
    • b0530eb1191307e9038d75e5c83973a396137681 and later · before 9830999c9e065c1813ec5435bfe4eab98ee54a87affected · git
    • b0530eb1191307e9038d75e5c83973a396137681 and later · before c5735c7d0eef7a5240f9c1c66e44ba52a1be58d6affected · git
    • b0530eb1191307e9038d75e5c83973a396137681 and later · before 0f7dd5839cfabaf9c007fb718ec66e907a473c93affected · git
    • b0530eb1191307e9038d75e5c83973a396137681 and later · before 0ccf4f27b4652570b5de3de02a89a86435559de9affected · git
    • b0530eb1191307e9038d75e5c83973a396137681 and later · before bc1dccc518cc5ab5140fba06c27e7188e0ed342baffected · git
    • before 5.9not affected · semver
    • 6.1.175 and later · up to and including 6.1.*not affected · semver
    • 6.6.141 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.94-16.12.94-1
Debian:14linuxbefore 7.0.10-17.0.10-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53052Jun 24, 2026 · ASoC: qcom: qdsp6: topology: check widget type before accessing data
    22Monitor
  • ← EarlierCVE-2026-53054Jun 24, 2026 · drm/msm: Fix VM_BIND UNMAP locking
    31Monitor
  • Later →CVE-2026-53057Jun 24, 2026 · iommu/riscv: Add IOTINVAL after updating DDT/PDT entries
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0ccf4f27b4652570b5de3de02a89a86435559de9Vendor (CNA)
Linux Linux0f7dd5839cfabaf9c007fb718ec66e907a473c93Vendor (CNA)
Linux Linux1181a7028d37e0b1e720a36125a03f5db97e3d27Vendor (CNA)
Linux Linux9830999c9e065c1813ec5435bfe4eab98ee54a87Vendor (CNA)
Linux Linuxbc1dccc518cc5ab5140fba06c27e7188e0ed342bVendor (CNA)
Linux Linuxc5735c7d0eef7a5240f9c1c66e44ba52a1be58d6Vendor (CNA)
azl3 kernel 6.6.139.1-1 on Azure Linux 3.06.6.143.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records