[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061828-CVE-2025-38041-7d47@gregkh>
Date: Wed, 18 Jun 2025 11:33:37 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38041: clk: sunxi-ng: h616: Reparent GPU clock during frequency changes
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
clk: sunxi-ng: h616: Reparent GPU clock during frequency changes
The H616 manual does not state that the GPU PLL supports
dynamic frequency configuration, so we must take extra care when changing
the frequency. Currently any attempt to do device DVFS on the GPU lead
to panfrost various ooops, and GPU hangs.
The manual describes the algorithm for changing the PLL
frequency, which the CPU PLL notifier code already support, so we reuse
that to reparent the GPU clock to GPU1 clock during frequency
changes.
The Linux kernel CVE team has assigned CVE-2025-38041 to this issue.
Affected and fixed versions
===========================
Fixed in 6.14.9 with commit 1439673b78185eaaa5fae444b3a9d58c434ee78e
Fixed in 6.15 with commit eb963d7948ce6571939c6875424b557b25f16610
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-38041
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/clk/sunxi-ng/ccu-sun50i-h616.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/1439673b78185eaaa5fae444b3a9d58c434ee78e
https://git.kernel.org/stable/c/eb963d7948ce6571939c6875424b557b25f16610
Powered by blists - more mailing lists