<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T14:17:23.550043+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-64213</id>
    <title>CVE-2026-64213 — hwmon: (lm90) Add lock protection to lm90_alert</title>
    <updated>2026-09-29T14:17:24.083808+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>hwmon: (lm90) Add lock protection to lm90_alert</p>
<p>Sashiko reports:</p>
<p>lm90_alert() executes in the smbus alert context and calls
lm90_update_confreg() to disable the hardware alert line, without
acquiring hwmon_lock.</p>
<p>Concurrently, sysfs write operations (such as lm90_write_convrate) hold
the hwmon_lock, temporarily modify data-&gt;config, and then restore it.</p>
<p>If an alert interrupt occurs concurrently with a sysfs write, the sysfs
path will overwrite the alert handler's modifications to data-&gt;config
and the hardware register.</p>
<p>This unintentionally re-enables the hardware alert line while the alarm is
still active, causing an interrupt storm.</p>
<p>Add the missing lock to lm90_alert() to solve the problem.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64213"/>
  </entry>
</feed>
