CVE-2026-80746: clk: qcom: dispcc-eliza: Fix disp_cc_mdss_mdp_clk_src RCG stall on Eliza EVK
In the Linux kernel, the following vulnerability has been resolved:
clk: qcom: dispcc-eliza: Fix dispccmdssmdpclksrc RCG stall on Eliza EVK
Eliza EVK (eliza-cqs-evk.dts) does not have display enabled, however its Display Clock Controller is enabled and references parent clocks from DSI PHYs, which causes clock reparenting issues during probe (init) and warning on Eliza EVK:
dispccmdssmdpclksrc: rcg didn't update its configuration. WARNING: drivers/clk/qcom/clk-rcg2.c:136 at updateconfig+0xd4/0xe4, CPU#1: udevd/273 ... updateconfig (drivers/clk/qcom/clk-rcg2.c:136 (discriminator 2)) (P) clkrcg2shareddisable (drivers/clk/qcom/clk-rcg2.c:1471) clkrcg2sharedinit (drivers/clk/qcom/clk-rcg2.c:1540) clkregister (drivers/clk/clk.c:3959 drivers/clk/clk.c:4368) devmclkhwregister (drivers/clk/clk.c:4448 (discriminator 1) drivers/clk/clk.c:4672 (discriminator 1)) devmclkregisterregmap (drivers/clk/qcom/clk-regmap.c:104) qcomccreallyprobe (drivers/clk/qcom/common.c:418) qcomccprobe (drivers/clk/qcom/common.c:445) dispccelizaprobe (dispcc-eliza.c:?) dispcceliza platformprobe (drivers/base/platform.c:1432)
Affected Software
Event History
Frequently Asked Questions
Which systems are affected by the reported clock-controller stall?
The issue is reported for the Eliza EVK using the eliza-cqs-evk.dts device tree. That configuration has display disabled while the Display Clock Controller remains enabled and references parent clocks from DSI PHYs.
When does the problem occur and how can it be identified?
It occurs during Display Clock Controller probe and initialization, when clock reparenting causes disp_cc_mdss_mdp_clk_src to fail to update its configuration. Affected systems may log the warning "disp_cc_mdss_mdp_clk_src: rcg didn't update its configuration" with a stack trace through update_config, clk_rcg2_shared_init, and disp_cc_eliza_probe.
What remediation is available?
The issue is marked resolved in the Linux kernel. The provided stable-kernel references identify the fixes: 9114f72b91618b89a390a64d6c92765e14d555ae and 2ef00630c5c0b7b2c08aba7643f47594952d357e.