<?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>Fri, 02 Oct 2026 01:45:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-35986 — phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-35986</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;phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered&lt;/p&gt;
&lt;p&gt;The power_supply frame-work is not really designed for there to be
long living in kernel references to power_supply devices.&lt;/p&gt;
&lt;p&gt;Specifically unregistering a power_supply while some other code has
a reference to it triggers a WARN in power_supply_unregister():&lt;/p&gt;
&lt;p&gt;WARN_ON(atomic_dec_return(&amp;amp;psy-&amp;gt;use_cnt));&lt;/p&gt;
&lt;p&gt;Folllowed by the power_supply still getting removed and the
backing data freed anyway, leaving the tusb1210 charger-detect code
with a dangling reference, resulting in a crash the next time
tusb1210_get_online() is called.&lt;/p&gt;
&lt;p&gt;Fix this by only holding the reference in tusb1210_get_online()
freeing it at the end of the function. Note this still leaves
a theoretical race window, but it avoids the issue when manually
rmmod-ing the charger chip driver during development.&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;phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered&lt;/p&gt;
&lt;p&gt;The power_supply frame-work is not really designed for there to be
long living in kernel references to power_supply devices.&lt;/p&gt;
&lt;p&gt;Specifically unregistering a power_supply while some other code has
a reference to it triggers a WARN in power_supply_unregister():&lt;/p&gt;
&lt;p&gt;WARN_ON(atomic_dec_return(&amp;amp;psy-&amp;gt;use_cnt));&lt;/p&gt;
&lt;p&gt;Folllowed by the power_supply still getting removed and the
backing data freed anyway, leaving the tusb1210 charger-detect code
with a dangling reference, resulting in a crash the next time
tusb1210_get_online() is called.&lt;/p&gt;
&lt;p&gt;Fix this by only holding the reference in tusb1210_get_online()
freeing it at the end of the function. Note this still leaves
a theoretical race window, but it avoids the issue when manually
rmmod-ing the charger chip driver during development.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-35986</guid>
    </item>
  </channel>
</rss>
