From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-53019: clk: spacemit: ccu_mix: fix inverted condition in ccu_mix_trigger_fc()
Date: Wed, 24 Jun 2026 17:30:43 +0100 [thread overview]
Message-ID: <2026062451-CVE-2026-53019-9d74@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
clk: spacemit: ccu_mix: fix inverted condition in ccu_mix_trigger_fc()
Fix inverted condition that skips frequency change trigger,
causing kernel panics during cpufreq scaling.
The Linux kernel CVE team has assigned CVE-2026-53019 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit 1b72c59db0add8e47fa116b21f78ed0b09a264f3 and fixed in 6.18.33 with commit da99d0302d3ccccfb13c69e663bf8eae698b9562
Issue introduced in 6.16 with commit 1b72c59db0add8e47fa116b21f78ed0b09a264f3 and fixed in 7.0.10 with commit 16dfbc4e95c46dd9c79cb8d550c7f267d4a79b91
Issue introduced in 6.16 with commit 1b72c59db0add8e47fa116b21f78ed0b09a264f3 and fixed in 7.1 with commit 54e97360b44bed6b4399dd3be3d65f392df940fa
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-2026-53019
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/spacemit/ccu_mix.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/da99d0302d3ccccfb13c69e663bf8eae698b9562
https://git.kernel.org/stable/c/16dfbc4e95c46dd9c79cb8d550c7f267d4a79b91
https://git.kernel.org/stable/c/54e97360b44bed6b4399dd3be3d65f392df940fa
reply other threads:[~2026-06-24 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026062451-CVE-2026-53019-9d74@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.