<?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 11:30:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89464 — power: supply: twl4030_charger: cancel workers via devm</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89464</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: twl4030_charger: cancel workers via devm&lt;/p&gt;
&lt;p&gt;bci is devm-allocated. Two workers (bci-&amp;gt;work and bci-&amp;gt;current_worker)
dereference it. twl4030_bci_remove() disables charging and masks
interrupts. It cancels neither worker. A worker pending at remove() can
run after devm frees bci.&lt;/p&gt;
&lt;p&gt;The USB transceiver comes from devm_usb_get_phy_by_node(). devm
unregisters its notifier only after remove() returns. A cancel_work_sync()
in remove() can then race a notifier reschedule. devm_work_autocancel()
and devm_delayed_work_autocancel() avoid that. They cancel the workers
during devm release, before bci is freed.&lt;/p&gt;
&lt;p&gt;The current_worker is registered first, since devm will cancel in
reverse order and bci-&amp;gt;work can reschedule current_worker.&lt;/p&gt;
&lt;p&gt;[Move comment about order into the commit message]&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: twl4030_charger: cancel workers via devm&lt;/p&gt;
&lt;p&gt;bci is devm-allocated. Two workers (bci-&amp;gt;work and bci-&amp;gt;current_worker)
dereference it. twl4030_bci_remove() disables charging and masks
interrupts. It cancels neither worker. A worker pending at remove() can
run after devm frees bci.&lt;/p&gt;
&lt;p&gt;The USB transceiver comes from devm_usb_get_phy_by_node(). devm
unregisters its notifier only after remove() returns. A cancel_work_sync()
in remove() can then race a notifier reschedule. devm_work_autocancel()
and devm_delayed_work_autocancel() avoid that. They cancel the workers
during devm release, before bci is freed.&lt;/p&gt;
&lt;p&gt;The current_worker is registered first, since devm will cancel in
reverse order and bci-&amp;gt;work can reschedule current_worker.&lt;/p&gt;
&lt;p&gt;[Move comment about order into the commit message]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89464</guid>
    </item>
  </channel>
</rss>
