During a DPU runtime suspend, a call to dev_pm_opp_set_rate(dev, 0) lowers the MMCX rail to its minimum voltage while the core clock remains at a high frequency. When the device resumes, the clock is re‑enabled without restoring the proper voltage level, leaving the rail unable to sustain the clock rate. This mismatch can cause unpredictable behavior, instability, or a full system crash. The issue is a local resource‑management flaw that directly impacts the availability of the affected device.

The flaw resides in the Linux kernel's drm/msm/dpu driver, which powers many Qualcomm and related SoC graphics engines. Any Linux system employing this driver—particularly those running newer kernel versions compiled with DPU support—could be impacted. The exact kernel release range is not specified, so all devices using the unpatched DPU path should be considered potentially vulnerable.

The EPSS score is not available and the flaw is not listed in the CISA KEV catalog, so the baseline exploitation probability remains uncertain. Nonetheless, the vulnerability provides a local denial‑of‑service vector: an attacker who can trigger a runtime suspend/resume cycle (e.g., through a privileged application or a trusted driver) can cause the affected system to crash. There is no evidence of a remote attack surface or privilege escalation in the supplied description, making the risk primarily a local availability concern.