<?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>Wed, 30 Sep 2026 12:31:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50250 — regulator: core: fix use_count leakage when handling boot-on</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50250</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;regulator: core: fix use_count leakage when handling boot-on&lt;/p&gt;
&lt;p&gt;I found a use_count leakage towards supply regulator of rdev with
boot-on option.&lt;/p&gt;
&lt;p&gt;┌───────────────────┐           ┌───────────────────┐
│  regulator_dev A  │           │  regulator_dev B  │
│     (boot-on)     │           │     (boot-on)     │
│    use_count=0    │◀──supply──│    use_count=1    │
│                   │           │                   │
└───────────────────┘           └───────────────────┘&lt;/p&gt;
&lt;p&gt;In case of rdev(A) configured with `regulator-boot-on&amp;#39;, the use_count
of supplying regulator(B) will increment inside
regulator_enable(rdev-&amp;gt;supply).&lt;/p&gt;
&lt;p&gt;Thus, B will acts like always-on, and further balanced
regulator_enable/disable cannot actually disable it anymore.&lt;/p&gt;
&lt;p&gt;However, B was also configured with `regulator-boot-on&amp;#39;, we wish it
could be disabled afterwards.&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;regulator: core: fix use_count leakage when handling boot-on&lt;/p&gt;
&lt;p&gt;I found a use_count leakage towards supply regulator of rdev with
boot-on option.&lt;/p&gt;
&lt;p&gt;┌───────────────────┐           ┌───────────────────┐
│  regulator_dev A  │           │  regulator_dev B  │
│     (boot-on)     │           │     (boot-on)     │
│    use_count=0    │◀──supply──│    use_count=1    │
│                   │           │                   │
└───────────────────┘           └───────────────────┘&lt;/p&gt;
&lt;p&gt;In case of rdev(A) configured with `regulator-boot-on&amp;#39;, the use_count
of supplying regulator(B) will increment inside
regulator_enable(rdev-&amp;gt;supply).&lt;/p&gt;
&lt;p&gt;Thus, B will acts like always-on, and further balanced
regulator_enable/disable cannot actually disable it anymore.&lt;/p&gt;
&lt;p&gt;However, B was also configured with `regulator-boot-on&amp;#39;, we wish it
could be disabled afterwards.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50250</guid>
    </item>
  </channel>
</rss>
