<?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>Mon, 28 Sep 2026 07:56:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54079 — power: supply: bq27xxx: Fix poll_interval handling and races on remove</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54079</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: bq27xxx: Fix poll_interval handling and races on remove&lt;/p&gt;
&lt;p&gt;Before this patch bq27xxx_battery_teardown() was setting poll_interval = 0
to avoid bq27xxx_battery_update() requeuing the delayed_work item.&lt;/p&gt;
&lt;p&gt;There are 2 problems with this:&lt;/p&gt;
&lt;p&gt;1. If the driver is unbound through sysfs, rather then the module being
   rmmod-ed, this changes poll_interval unexpectedly&lt;/p&gt;
&lt;p&gt;2. This is racy, after it being set poll_interval could be changed
   before bq27xxx_battery_update() checks it through
   /sys/module/bq27xxx_battery/parameters/poll_interval&lt;/p&gt;
&lt;p&gt;Fix this by added a removed attribute to struct bq27xxx_device_info and
using that instead of setting poll_interval to 0.&lt;/p&gt;
&lt;p&gt;There also is another poll_interval related race on remove(), writing
/sys/module/bq27xxx_battery/parameters/poll_interval will requeue
the delayed_work item for all devices on the bq27xxx_battery_devices
list and the device being removed was only removed from that list
after cancelling the delayed_work item.&lt;/p&gt;
&lt;p&gt;Fix this by moving the removal from the bq27xxx_battery_devices list
to before cancelling the delayed_work item.&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: bq27xxx: Fix poll_interval handling and races on remove&lt;/p&gt;
&lt;p&gt;Before this patch bq27xxx_battery_teardown() was setting poll_interval = 0
to avoid bq27xxx_battery_update() requeuing the delayed_work item.&lt;/p&gt;
&lt;p&gt;There are 2 problems with this:&lt;/p&gt;
&lt;p&gt;1. If the driver is unbound through sysfs, rather then the module being
   rmmod-ed, this changes poll_interval unexpectedly&lt;/p&gt;
&lt;p&gt;2. This is racy, after it being set poll_interval could be changed
   before bq27xxx_battery_update() checks it through
   /sys/module/bq27xxx_battery/parameters/poll_interval&lt;/p&gt;
&lt;p&gt;Fix this by added a removed attribute to struct bq27xxx_device_info and
using that instead of setting poll_interval to 0.&lt;/p&gt;
&lt;p&gt;There also is another poll_interval related race on remove(), writing
/sys/module/bq27xxx_battery/parameters/poll_interval will requeue
the delayed_work item for all devices on the bq27xxx_battery_devices
list and the device being removed was only removed from that list
after cancelling the delayed_work item.&lt;/p&gt;
&lt;p&gt;Fix this by moving the removal from the bq27xxx_battery_devices list
to before cancelling the delayed_work item.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-54079</guid>
    </item>
  </channel>
</rss>
