<?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 17:56:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74552 — hwmon: (lm90) Only report alarms if driver is ready</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74552</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) Only report alarms if driver is ready&lt;/p&gt;
&lt;p&gt;Userspace can read sysfs attributes before driver registration is complete,
immediately after devm_hwmon_device_register_with_info() has been called.
At that time, data-&amp;gt;hwmon_dev is not yet initialized. This can trigger
a NULL pointer access since lm90_update_device() and with it
lm90_update_alarms_locked() will be called. This call schedules
report_work and lm90_report_alarms(), which passes the still-NULL
data-&amp;gt;hwmon_dev to hwmon_notify_event() and triggers a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;Fix the problem by only scheduling the report and alert workers
data-&amp;gt;hwmon_dev is set.&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) Only report alarms if driver is ready&lt;/p&gt;
&lt;p&gt;Userspace can read sysfs attributes before driver registration is complete,
immediately after devm_hwmon_device_register_with_info() has been called.
At that time, data-&amp;gt;hwmon_dev is not yet initialized. This can trigger
a NULL pointer access since lm90_update_device() and with it
lm90_update_alarms_locked() will be called. This call schedules
report_work and lm90_report_alarms(), which passes the still-NULL
data-&amp;gt;hwmon_dev to hwmon_notify_event() and triggers a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;Fix the problem by only scheduling the report and alert workers
data-&amp;gt;hwmon_dev is set.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74552</guid>
    </item>
  </channel>
</rss>
