<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 02:49:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-27002 — clk: mediatek: Do a runtime PM get on controllers during probe</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-27002</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;clk: mediatek: Do a runtime PM get on controllers during probe&lt;/p&gt;
&lt;p&gt;mt8183-mfgcfg has a mutual dependency with genpd during the probing
stage, which leads to a deadlock in the following call stack:&lt;/p&gt;
&lt;p&gt;CPU0:  genpd_lock --&amp;gt; clk_prepare_lock
genpd_power_off_work_fn()
 genpd_lock()
 generic_pm_domain::power_off()
    clk_unprepare()
      clk_prepare_lock()&lt;/p&gt;
&lt;p&gt;CPU1: clk_prepare_lock --&amp;gt; genpd_lock
clk_register()
  __clk_core_init()
    clk_prepare_lock()
    clk_pm_runtime_get()
      genpd_lock()&lt;/p&gt;
&lt;p&gt;Do a runtime PM get at the probe function to make sure clk_register()
won&amp;#39;t acquire the genpd lock. Instead of only modifying mt8183-mfgcfg,
do this on all mediatek clock controller probings because we don&amp;#39;t
believe this would cause any regression.&lt;/p&gt;
&lt;p&gt;Verified on MT8183 and MT8192 Chromebooks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;clk: mediatek: Do a runtime PM get on controllers during probe&lt;/p&gt;
&lt;p&gt;mt8183-mfgcfg has a mutual dependency with genpd during the probing
stage, which leads to a deadlock in the following call stack:&lt;/p&gt;
&lt;p&gt;CPU0:  genpd_lock --&amp;gt; clk_prepare_lock
genpd_power_off_work_fn()
 genpd_lock()
 generic_pm_domain::power_off()
    clk_unprepare()
      clk_prepare_lock()&lt;/p&gt;
&lt;p&gt;CPU1: clk_prepare_lock --&amp;gt; genpd_lock
clk_register()
  __clk_core_init()
    clk_prepare_lock()
    clk_pm_runtime_get()
      genpd_lock()&lt;/p&gt;
&lt;p&gt;Do a runtime PM get at the probe function to make sure clk_register()
won&amp;#39;t acquire the genpd lock. Instead of only modifying mt8183-mfgcfg,
do this on all mediatek clock controller probings because we don&amp;#39;t
believe this would cause any regression.&lt;/p&gt;
&lt;p&gt;Verified on MT8183 and MT8192 Chromebooks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-27002</guid>
    </item>
  </channel>
</rss>
