<?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 08:42:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64213 — hwmon: (lm90) Add lock protection to lm90_alert</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64213</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;hwmon: (lm90) Add lock protection to lm90_alert&lt;/p&gt;
&lt;p&gt;Sashiko reports:&lt;/p&gt;
&lt;p&gt;lm90_alert() executes in the smbus alert context and calls
lm90_update_confreg() to disable the hardware alert line, without
acquiring hwmon_lock.&lt;/p&gt;
&lt;p&gt;Concurrently, sysfs write operations (such as lm90_write_convrate) hold
the hwmon_lock, temporarily modify data-&amp;gt;config, and then restore it.&lt;/p&gt;
&lt;p&gt;If an alert interrupt occurs concurrently with a sysfs write, the sysfs
path will overwrite the alert handler&amp;#39;s modifications to data-&amp;gt;config
and the hardware register.&lt;/p&gt;
&lt;p&gt;This unintentionally re-enables the hardware alert line while the alarm is
still active, causing an interrupt storm.&lt;/p&gt;
&lt;p&gt;Add the missing lock to lm90_alert() to solve the problem.&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;hwmon: (lm90) Add lock protection to lm90_alert&lt;/p&gt;
&lt;p&gt;Sashiko reports:&lt;/p&gt;
&lt;p&gt;lm90_alert() executes in the smbus alert context and calls
lm90_update_confreg() to disable the hardware alert line, without
acquiring hwmon_lock.&lt;/p&gt;
&lt;p&gt;Concurrently, sysfs write operations (such as lm90_write_convrate) hold
the hwmon_lock, temporarily modify data-&amp;gt;config, and then restore it.&lt;/p&gt;
&lt;p&gt;If an alert interrupt occurs concurrently with a sysfs write, the sysfs
path will overwrite the alert handler&amp;#39;s modifications to data-&amp;gt;config
and the hardware register.&lt;/p&gt;
&lt;p&gt;This unintentionally re-enables the hardware alert line while the alarm is
still active, causing an interrupt storm.&lt;/p&gt;
&lt;p&gt;Add the missing lock to lm90_alert() to solve the problem.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64213</guid>
    </item>
  </channel>
</rss>
