UBUNTU-CVE-2026-46247: Medium severity ubuntu/linux-azure vulnerability
In the Linux kernel, the following vulnerability has been resolved: clk: qcom: gfx3d: add parent to parent request map After commit d228ece36345 ("clk: divider: remove roundrate() in favor of determinerate()") determining GFX3D clock rate crashes, because the passed parent map doesn't provide the expected bestparenthw clock (with the rounddrate path before the offending commit the bestparenthw was ignored). Set the field in parentreq in addition to setting it in the req, fixing the crash. clkhwroundrate (drivers/clk/clk.c:1764) (P) clkdividerbestdiv (drivers/clk/clk-divider.c:336) dividerdeterminerate (drivers/clk/clk-divider.c:358) clkalphapllpostdivdeterminerate (drivers/clk/qcom/clk-alpha-pll.c:1275) clkcoredetermineroundnolock (drivers/clk/clk.c:1606) clkcoreroundratenolock (drivers/clk/clk.c:1701) clkdeterminerate (drivers/clk/clk.c:1741) clkgfx3ddeterminerate (drivers/clk/qcom/clk-rcg2.c:1268) clkcoredetermineroundnolock (drivers/clk/clk.c:1606) clkcoreroundratenolock (drivers/clk/clk.c:1701) clkcoreroundratenolock (drivers/clk/clk.c:1710) clkroundrate (drivers/clk/clk.c:1804) devpmoppsetrate (drivers/opp/core.c:1440 (discriminator 1)) msmdevfreqtarget (drivers/gpu/drm/msm/msmgpudevfreq.c:51) devfreqsettarget (drivers/devfreq/devfreq.c:360) devfrequpdatetarget (drivers/devfreq/devfreq.c:426) devfreqmonitor (drivers/devfreq/devfreq.c:458) processonework (arch/arm64/include/asm/jumplabel.h:36 include/trace/events/workqueue.h:110 kernel/workqueue.c:3284) workerthread (kernel/workqueue.c:3356 (discriminator 2) kernel/workqueue.c:3443 (discriminator 2)) kthread (kernel/kthread.c:467) retfromfork (arch/arm64/kernel/entry.S:861)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-aws-6.8to a version that resolves this vulnerability.Fixed in 6.8.0-1060.63~22.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-6.8to a version that resolves this vulnerability.Fixed in 6.8.0-1063.71~22.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fde-6.8to a version that resolves this vulnerability.Fixed in 6.8.0-1062.69~22.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-6.8to a version that resolves this vulnerability.Fixed in 6.8.0-1063.69~22.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-6.8to a version that resolves this vulnerability.Fixed in 6.8.0-136.136~22.04.1 - Upgrade
Upgrade
ubuntu/linux-ibm-6.8to a version that resolves this vulnerability.Fixed in 6.8.0-1060.61~22.04.1 - Upgrade
Upgrade
ubuntu/linux-lowlatency-hwe-6.8to a version that resolves this vulnerability.Fixed in 6.8.0-134.134.1~22.04.1 - Upgrade
Upgrade
ubuntu/linux-nvidia-6.8to a version that resolves this vulnerability.Fixed in 6.8.0-1058.61~22.04.1 - Upgrade
Upgrade
ubuntu/linux-oracle-6.8to a version that resolves this vulnerability.Fixed in 6.8.0-1057.58~22.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-6.8to a version that resolves this vulnerability.Fixed in 6.8.0-134.134~22.04.1 - Upgrade
Upgrade
ubuntu/linux-realtime-6.8to a version that resolves this vulnerability.Fixed in 6.8.1-1055.56~22.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 6.8.0-134.134 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 6.8.0-1060.63 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 6.8.0-1063.71 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 6.8.0-1062.69 - Upgrade
Upgrade
ubuntu/linux-azure-nvidiato a version that resolves this vulnerability.Fixed in 6.8.0-1039.42 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 6.8.0-1063.69 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 6.8.0-1058.64 - Upgrade
Upgrade
ubuntu/linux-gkeopto a version that resolves this vulnerability.Fixed in 6.8.0-1045.48 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 6.8.0-1060.61 - Upgrade
Upgrade
ubuntu/linux-lowlatencyto a version that resolves this vulnerability.Fixed in 6.8.0-134.134.1 - Upgrade
Upgrade
ubuntu/linux-nvidiato a version that resolves this vulnerability.Fixed in 6.8.0-1058.61 - Upgrade
Upgrade
ubuntu/linux-nvidia-lowlatencyto a version that resolves this vulnerability.Fixed in 6.8.0-1058.61.1 - Upgrade
Upgrade
ubuntu/linux-nvidia-tegrato a version that resolves this vulnerability.Fixed in 6.8.0-1029.30 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 6.8.0-1057.58 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 6.8.0-1060.64 - Upgrade
Upgrade
ubuntu/linux-xilinxto a version that resolves this vulnerability.Fixed in 6.8.0-1032.33 - Upgrade
Upgrade
ubuntu/linux-bluefieldto a version that resolves this vulnerability.Fixed in 6.8.0-1026.30 - Upgrade
Upgrade
ubuntu/linux-raspi-realtimeto a version that resolves this vulnerability.Fixed in 6.8.0-2049.50 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 6.8.1-1055.56 - Upgrade
Upgrade
ubuntu/linux-aws-fipsto a version that resolves this vulnerability.Fixed in 6.8.0-1060.63+fips1 - Upgrade
Upgrade
ubuntu/linux-azure-fipsto a version that resolves this vulnerability.Fixed in 6.8.0-1062.69+fips1 - Upgrade
Upgrade
ubuntu/linux-fipsto a version that resolves this vulnerability.Fixed in 6.8.0-134.134+fips1 - Upgrade
Upgrade
ubuntu/linux-gcp-fipsto a version that resolves this vulnerability.Fixed in 6.8.0-1063.69+fips1 - Compensating control
In the Qualcomm GFX3D clock parent request handling, set the parent clock in the parent_req map in addition to setting it in the request (req), so the expected best_parent_hw clock is provided and determining the GFX3D clock rate does not crash.
Event History
Frequently Asked Questions
Which systems are most likely to encounter this issue?
Systems using the Qualcomm GFX3D clock driver are implicated, because the crash occurs while determining the GFX3D clock rate. The affected Ubuntu kernel package list includes linux, linux-azure, linux-aws-fips, linux-azure-fips, linux-fips, linux-gcp-fips, linux-gcp, and linux-oracle.
What event triggers the failure?
The failure is triggered when the kernel determines or rounds the GFX3D clock rate. The supplied stack trace shows this can occur through dev_pm_opp_set_rate during clock-rate selection.
How can an administrator recognize the issue?
A system experiencing this issue can crash while determining the GFX3D clock rate. Kernel stack traces may include clk_hw_round_rate, clk_divider_bestdiv, divider_determine_rate, clk_gfx3d_determine_rate, and dev_pm_opp_set_rate.