Linux kernel CVE announcements
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46247: clk: qcom: gfx3d: add parent to parent request map
Date: Wed,  3 Jun 2026 17:49:36 +0200	[thread overview]
Message-ID: <2026060333-CVE-2026-46247-4daa@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

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 round_rate() in favor
of determine_rate()") determining GFX3D clock rate crashes, because the
passed parent map doesn't provide the expected best_parent_hw clock
(with the roundd_rate path before the offending commit the
best_parent_hw was ignored).

Set the field in parent_req in addition to setting it in the req,
fixing the crash.

 clk_hw_round_rate (drivers/clk/clk.c:1764) (P)
 clk_divider_bestdiv (drivers/clk/clk-divider.c:336)
 divider_determine_rate (drivers/clk/clk-divider.c:358)
 clk_alpha_pll_postdiv_determine_rate (drivers/clk/qcom/clk-alpha-pll.c:1275)
 clk_core_determine_round_nolock (drivers/clk/clk.c:1606)
 clk_core_round_rate_nolock (drivers/clk/clk.c:1701)
 __clk_determine_rate (drivers/clk/clk.c:1741)
 clk_gfx3d_determine_rate (drivers/clk/qcom/clk-rcg2.c:1268)
 clk_core_determine_round_nolock (drivers/clk/clk.c:1606)
 clk_core_round_rate_nolock (drivers/clk/clk.c:1701)
 clk_core_round_rate_nolock (drivers/clk/clk.c:1710)
 clk_round_rate (drivers/clk/clk.c:1804)
 dev_pm_opp_set_rate (drivers/opp/core.c:1440 (discriminator 1))
 msm_devfreq_target (drivers/gpu/drm/msm/msm_gpu_devfreq.c:51)
 devfreq_set_target (drivers/devfreq/devfreq.c:360)
 devfreq_update_target (drivers/devfreq/devfreq.c:426)
 devfreq_monitor (drivers/devfreq/devfreq.c:458)
 process_one_work (arch/arm64/include/asm/jump_label.h:36 include/trace/events/workqueue.h:110 kernel/workqueue.c:3284)
 worker_thread (kernel/workqueue.c:3356 (discriminator 2) kernel/workqueue.c:3443 (discriminator 2))
 kthread (kernel/kthread.c:467)
 ret_from_fork (arch/arm64/kernel/entry.S:861)

The Linux kernel CVE team has assigned CVE-2026-46247 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.5 with commit 55213e1acec9218580c90d36034aa0370a51daab and fixed in 6.1.165 with commit 82cfe5292b11deb1dc33822f67f73cfbe8eafe25
	Issue introduced in 4.5 with commit 55213e1acec9218580c90d36034aa0370a51daab and fixed in 6.6.128 with commit 547ae2f17349c7586953af5ef50de43ef3f65e9e
	Issue introduced in 4.5 with commit 55213e1acec9218580c90d36034aa0370a51daab and fixed in 6.12.75 with commit 56360aa4ddd736fc19e6d0b0206c5e437e0d6ff8
	Issue introduced in 4.5 with commit 55213e1acec9218580c90d36034aa0370a51daab and fixed in 6.18.14 with commit aed53da569fb96eec09b4817b1953bcc2e467eea
	Issue introduced in 4.5 with commit 55213e1acec9218580c90d36034aa0370a51daab and fixed in 6.19.4 with commit 8aa972eba1f29068d13bec716d33abca30fb3f2a
	Issue introduced in 4.5 with commit 55213e1acec9218580c90d36034aa0370a51daab and fixed in 7.0 with commit 2583cb925ca1ce450aa5d74a05a67448db970193

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-46247
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/qcom/clk-rcg2.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/82cfe5292b11deb1dc33822f67f73cfbe8eafe25
	https://git.kernel.org/stable/c/547ae2f17349c7586953af5ef50de43ef3f65e9e
	https://git.kernel.org/stable/c/56360aa4ddd736fc19e6d0b0206c5e437e0d6ff8
	https://git.kernel.org/stable/c/aed53da569fb96eec09b4817b1953bcc2e467eea
	https://git.kernel.org/stable/c/8aa972eba1f29068d13bec716d33abca30fb3f2a
	https://git.kernel.org/stable/c/2583cb925ca1ce450aa5d74a05a67448db970193

                 reply	other threads:[~2026-06-03 15:52 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=2026060333-CVE-2026-46247-4daa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox