<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 15:17:46 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80660</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-80660</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-80660</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1286 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1286</link>
      <description>certfr-2026-avi-1286</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1286</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80660</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80660</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: hwmon: (occ) unregister sysfs devices outside occ lock occ_active(false) and occ_shutdown() unregister sysfs-backed devices while occ-&amp;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-&amp;gt;lock again.  That gives the unregister paths the lock ordering occ-&amp;gt;lock -&amp;gt; sysfs callback drain, while a callback has the opposite edge sysfs callback -&amp;gt; occ-&amp;gt;lock. This issue was found by our static analysis tool and then manually reviewed against the current tree. The grounded PoC kept the real unregister and callback carrier:   occ_shutdown()   hwmon_device_unregister()   occ_show_temp_1()   occ_update_response() Lockdep reported the circular dependency with occ_shutdown() already holding the OCC mutex and hwmon_device_unregister() waiting on the sysfs side:   WARNING: possible circular locking dependency detected   ... (sysfs_lock) ... at: hwmon_device_unregister+0x12/0x30 [vuln_msv]   ... (&amp;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 *** Serialize hwmon registration and removal with a separate hwmon_lock. Under that lock, detach occ-&amp;gt;hwmon and update occ-&amp;gt;active while occ-&amp;gt;lock is held so concurrent OCC state changes still see a stable state, then…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: hwmon: (occ) unregister sysfs devices outside occ lock occ_active(false) and occ_shutdown() unregister sysfs-backed devices while occ-&amp;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-&amp;gt;lock again.  That gives the unregister paths the lock ordering occ-&amp;gt;lock -&amp;gt; sysfs callback drain, while a callback has the opposite edge sysfs callback -&amp;gt; occ-&amp;gt;lock. This issue was found by our static analysis tool and then manually reviewed against the current tree. The grounded PoC kept the real unregister and callback carrier:   occ_shutdown()   hwmon_device_unregister()   occ_show_temp_1()   occ_update_response() Lockdep reported the circular dependency with occ_shutdown() already holding the OCC mutex and hwmon_device_unregister() waiting on the sysfs side:   WARNING: possible circular locking dependency detected   ... (sysfs_lock) ... at: hwmon_device_unregister+0x12/0x30 [vuln_msv]   ... (&amp;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 *** Serialize hwmon registration and removal with a separate hwmon_lock. Under that lock, detach occ-&amp;gt;hwmon and update occ-&amp;gt;active while occ-&amp;gt;lock is held so concurrent OCC state changes still see a stable state, then…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80660</guid>
    </item>
  </channel>
</rss>
