<?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>Sat, 03 Oct 2026 07:26:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72008 — pmdomain: mediatek: Fix possible nullptr KP in HWV cleanup/on-check</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72008</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;pmdomain: mediatek: Fix possible nullptr KP in HWV cleanup/on-check&lt;/p&gt;
&lt;p&gt;Should probe fail for HW_VOTER type power domains, this driver was
unconditionally trying to perform cleanup for DIRECT_CTL domains,
but only after checking if the target domain is powered on... with
the DIRECT_CTL scpsys_domain_is_on() code again.&lt;/p&gt;
&lt;p&gt;And there&amp;#39;s more: the scpsys_domain_is_on() function is also being
unconditionally used in the probe path, for any power domain that
has flag MTK_SCPD_KEEP_DEFAULT_OFF!&lt;/p&gt;
&lt;p&gt;This bug was never experienced by anyone because the HWV domains
never failed probe, and because none of those is declared with the
aforementioned flag - but it&amp;#39;s still something critical.&lt;/p&gt;
&lt;p&gt;In order to fix this, add a check for MTCMOS Type and, based on
that, call the correct functions for an &amp;#34;is on&amp;#34; check, and also
do the same for the cleanup path, calling the correct functions
for the &amp;#34;power off&amp;#34; action.&lt;/p&gt;
&lt;p&gt;For the latter, since there&amp;#39;s a call to pm_genpd_remove() right
before calling power_off, be cautious and add a variation of the
power off functions (with a _internal suffix) for those to get a
pointer to scpsys_domain instead of one to generic_pm_domain as,
even if that&amp;#39;s still working, this is way too much fragile and
would break at some point.&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;pmdomain: mediatek: Fix possible nullptr KP in HWV cleanup/on-check&lt;/p&gt;
&lt;p&gt;Should probe fail for HW_VOTER type power domains, this driver was
unconditionally trying to perform cleanup for DIRECT_CTL domains,
but only after checking if the target domain is powered on... with
the DIRECT_CTL scpsys_domain_is_on() code again.&lt;/p&gt;
&lt;p&gt;And there&amp;#39;s more: the scpsys_domain_is_on() function is also being
unconditionally used in the probe path, for any power domain that
has flag MTK_SCPD_KEEP_DEFAULT_OFF!&lt;/p&gt;
&lt;p&gt;This bug was never experienced by anyone because the HWV domains
never failed probe, and because none of those is declared with the
aforementioned flag - but it&amp;#39;s still something critical.&lt;/p&gt;
&lt;p&gt;In order to fix this, add a check for MTCMOS Type and, based on
that, call the correct functions for an &amp;#34;is on&amp;#34; check, and also
do the same for the cleanup path, calling the correct functions
for the &amp;#34;power off&amp;#34; action.&lt;/p&gt;
&lt;p&gt;For the latter, since there&amp;#39;s a call to pm_genpd_remove() right
before calling power_off, be cautious and add a variation of the
power off functions (with a _internal suffix) for those to get a
pointer to scpsys_domain instead of one to generic_pm_domain as,
even if that&amp;#39;s still working, this is way too much fragile and
would break at some point.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72008</guid>
    </item>
  </channel>
</rss>
