<?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-30T23:33:22.304010+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-80660</id>
    <title>CVE-2026-80660 — hwmon: (occ) unregister sysfs devices outside occ lock</title>
    <updated>2026-09-30T23:33:22.319060+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: (occ) unregister sysfs devices outside occ lock</p>
<p>occ_active(false) and occ_shutdown() unregister sysfs-backed devices while
occ-&gt;lock is held.  hwmon_device_unregister() and sysfs_remove_group() can
wait for active sysfs callbacks to drain, and those callbacks can enter the
OCC update path and try to take occ-&gt;lock again.  That gives the unregister
paths the lock ordering occ-&gt;lock -&gt; sysfs callback drain, while a callback
has the opposite edge sysfs callback -&gt; occ-&gt;lock.</p>
<p>This issue was found by our static analysis tool and then manually
reviewed against the current tree.</p>
<p>The grounded PoC kept the real unregister and callback carrier:</p>
<p>occ_shutdown()
  hwmon_device_unregister()
  occ_show_temp_1()
  occ_update_response()</p>
<p>Lockdep reported the circular dependency with occ_shutdown() already
holding the OCC mutex and hwmon_device_unregister() waiting on the sysfs
side:</p>
<p>WARNING: possible circular locking dependency detected
  ... (sysfs_lock) ... at: hwmon_device_unregister+0x12/0x30 [vuln_msv]
  ... (&amp;test_occ.lock) ... at: occ_shutdown.constprop.0+0xe/0x40 [vuln_msv]
  occ_update_response.isra.0+0xb/0x20 [vuln_msv]
  occ_show_temp_1.constprop.0.isra.0+0x23/0x40 [vuln_msv]
  *** DEADLOCK ***</p>
<p>Serialize hwmon registration and removal with a separate hwmon_lock.
Under that lock, detach occ-&gt;hwmon and update occ-&gt;active while occ-&gt;lock
is held so concurrent OCC state changes still see a stable sta…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-80660"/>
  </entry>
</feed>
