<?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>Thu, 01 Oct 2026 19:56:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53166 — power: supply: bq25890: Fix external_power_changed race</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53166</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;power: supply: bq25890: Fix external_power_changed race&lt;/p&gt;
&lt;p&gt;bq25890_charger_external_power_changed() dereferences bq-&amp;gt;charger,
which gets sets in bq25890_power_supply_init() like this:&lt;/p&gt;
&lt;p&gt;bq-&amp;gt;charger = devm_power_supply_register(bq-&amp;gt;dev, &amp;amp;bq-&amp;gt;desc, &amp;amp;psy_cfg);&lt;/p&gt;
&lt;p&gt;As soon as devm_power_supply_register() has called device_add()
the external_power_changed callback can get called. So there is a window
where bq25890_charger_external_power_changed() may get called while
bq-&amp;gt;charger has not been set yet leading to a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;This race hits during boot sometimes on a Lenovo Yoga Book 1 yb1-x90f
when the cht_wcove_pwrsrc (extcon) power_supply is done with detecting
the connected charger-type which happens to exactly hit the small window:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000018
  &amp;lt;snip&amp;gt;
  RIP: 0010:__power_supply_is_supplied_by+0xb/0xb0
  &amp;lt;snip&amp;gt;
  Call Trace:
   &amp;lt;TASK&amp;gt;
   __power_supply_get_supplier_property+0x19/0x50
   class_for_each_device+0xb1/0xe0
   power_supply_get_property_from_supplier+0x2e/0x50
   bq25890_charger_external_power_changed+0x38/0x1b0 [bq25890_charger]
   __power_supply_changed_work+0x30/0x40
   class_for_each_device+0xb1/0xe0
   power_supply_changed_work+0x5f/0xe0
  &amp;lt;snip&amp;gt;&lt;/p&gt;
&lt;p&gt;Fixing this is easy. The external_power_changed callback gets passed
the power_supply which will eventually get stored in bq-&amp;gt;charger,
so bq25890_charger_external_power_changed() can si…&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;power: supply: bq25890: Fix external_power_changed race&lt;/p&gt;
&lt;p&gt;bq25890_charger_external_power_changed() dereferences bq-&amp;gt;charger,
which gets sets in bq25890_power_supply_init() like this:&lt;/p&gt;
&lt;p&gt;bq-&amp;gt;charger = devm_power_supply_register(bq-&amp;gt;dev, &amp;amp;bq-&amp;gt;desc, &amp;amp;psy_cfg);&lt;/p&gt;
&lt;p&gt;As soon as devm_power_supply_register() has called device_add()
the external_power_changed callback can get called. So there is a window
where bq25890_charger_external_power_changed() may get called while
bq-&amp;gt;charger has not been set yet leading to a NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;This race hits during boot sometimes on a Lenovo Yoga Book 1 yb1-x90f
when the cht_wcove_pwrsrc (extcon) power_supply is done with detecting
the connected charger-type which happens to exactly hit the small window:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000018
  &amp;lt;snip&amp;gt;
  RIP: 0010:__power_supply_is_supplied_by+0xb/0xb0
  &amp;lt;snip&amp;gt;
  Call Trace:
   &amp;lt;TASK&amp;gt;
   __power_supply_get_supplier_property+0x19/0x50
   class_for_each_device+0xb1/0xe0
   power_supply_get_property_from_supplier+0x2e/0x50
   bq25890_charger_external_power_changed+0x38/0x1b0 [bq25890_charger]
   __power_supply_changed_work+0x30/0x40
   class_for_each_device+0xb1/0xe0
   power_supply_changed_work+0x5f/0xe0
  &amp;lt;snip&amp;gt;&lt;/p&gt;
&lt;p&gt;Fixing this is easy. The external_power_changed callback gets passed
the power_supply which will eventually get stored in bq-&amp;gt;charger,
so bq25890_charger_external_power_changed() can si…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53166</guid>
    </item>
  </channel>
</rss>
