<?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>Fri, 02 Oct 2026 10:52:03 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72125</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-72125</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://vulnerability.circl.lu/vuln/bell-cve-2026-72125</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1069 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1069</link>
      <description>certfr-2026-avi-1069</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1069</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72125</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-72125</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER&lt;/p&gt;
&lt;p&gt;isotp_release() looked up the bound network device via dev_get_by_index()
using the stored ifindex. During device unregistration the device is
unlisted from the ifindex hash before the NETDEV_UNREGISTER notifier
chain runs, so a concurrent isotp_release() could find no device, skip
can_rx_unregister() entirely, and still proceed to free the socket.
Since isotp_release() had already removed itself from the isotp
notifier list at that point, isotp_notify() would never get a chance to
clean up either, leaving a stale CAN filter that keeps pointing at the
freed socket.&lt;/p&gt;
&lt;p&gt;Fix this the same way raw.c already does: hold a tracked reference to
the bound net_device in the socket (so-&amp;gt;dev/so-&amp;gt;dev_tracker) from
bind() onward instead of re-resolving it from the ifindex, and
serialize bind()/release() with rtnl_lock() so that so-&amp;gt;dev is always
consistent with what the NETDEV_UNREGISTER notifier sees. so-&amp;gt;dev
stays valid regardless of ifindex-hash unlisting, and is only ever
cleared by whichever of isotp_release()/isotp_notify() gets there
first, so the filter is always removed exactly once.&lt;/p&gt;
&lt;p&gt;isotp_bind() now rejects a (re)bind with -EAGAIN while so-&amp;gt;[tx|rx].state
isn&amp;#39;t ISOTP_IDLE yet, so a timer left running by a prior
NETDEV_UNREGISTER can&amp;#39;t act on a newly bound so-&amp;gt;ifindex. Both checks
share the same lock_sock() section, so there is no window in whi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER&lt;/p&gt;
&lt;p&gt;isotp_release() looked up the bound network device via dev_get_by_index()
using the stored ifindex. During device unregistration the device is
unlisted from the ifindex hash before the NETDEV_UNREGISTER notifier
chain runs, so a concurrent isotp_release() could find no device, skip
can_rx_unregister() entirely, and still proceed to free the socket.
Since isotp_release() had already removed itself from the isotp
notifier list at that point, isotp_notify() would never get a chance to
clean up either, leaving a stale CAN filter that keeps pointing at the
freed socket.&lt;/p&gt;
&lt;p&gt;Fix this the same way raw.c already does: hold a tracked reference to
the bound net_device in the socket (so-&amp;gt;dev/so-&amp;gt;dev_tracker) from
bind() onward instead of re-resolving it from the ifindex, and
serialize bind()/release() with rtnl_lock() so that so-&amp;gt;dev is always
consistent with what the NETDEV_UNREGISTER notifier sees. so-&amp;gt;dev
stays valid regardless of ifindex-hash unlisting, and is only ever
cleared by whichever of isotp_release()/isotp_notify() gets there
first, so the filter is always removed exactly once.&lt;/p&gt;
&lt;p&gt;isotp_bind() now rejects a (re)bind with -EAGAIN while so-&amp;gt;[tx|rx].state
isn&amp;#39;t ISOTP_IDLE yet, so a timer left running by a prior
NETDEV_UNREGISTER can&amp;#39;t act on a newly bound so-&amp;gt;ifindex. Both checks
share the same lock_sock() section, so there is no window in whi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-72125</guid>
    </item>
    <item>
      <title>GHSA-37fw-xv85-q5fg</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-37fw-xv85-q5fg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER&lt;/p&gt;
&lt;p&gt;isotp_release() looked up the bound network device via dev_get_by_index()
using the stored ifindex. During device unregistration the device is
unlisted from the ifindex hash before the NETDEV_UNREGISTER notifier
chain runs, so a concurrent isotp_release() could find no device, skip
can_rx_unregister() entirely, and still proceed to free the socket.
Since isotp_release() had already removed itself from the isotp
notifier list at that point, isotp_notify() would never get a chance to
clean up either, leaving a stale CAN filter that keeps pointing at the
freed socket.&lt;/p&gt;
&lt;p&gt;Fix this the same way raw.c already does: hold a tracked reference to
the bound net_device in the socket (so-&amp;gt;dev/so-&amp;gt;dev_tracker) from
bind() onward instead of re-resolving it from the ifindex, and
serialize bind()/release() with rtnl_lock() so that so-&amp;gt;dev is always
consistent with what the NETDEV_UNREGISTER notifier sees. so-&amp;gt;dev
stays valid regardless of ifindex-hash unlisting, and is only ever
cleared by whichever of isotp_release()/isotp_notify() gets there
first, so the filter is always removed exactly once.&lt;/p&gt;
&lt;p&gt;isotp_bind() now rejects a (re)bind with -EAGAIN while so-&amp;gt;[tx|rx].state
isn&amp;#39;t ISOTP_IDLE yet, so a timer left running by a prior
NETDEV_UNREGISTER can&amp;#39;t act on a newly bound so-&amp;gt;ifindex. Both checks
share the same lock_sock() section, so there is no window in whi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER&lt;/p&gt;
&lt;p&gt;isotp_release() looked up the bound network device via dev_get_by_index()
using the stored ifindex. During device unregistration the device is
unlisted from the ifindex hash before the NETDEV_UNREGISTER notifier
chain runs, so a concurrent isotp_release() could find no device, skip
can_rx_unregister() entirely, and still proceed to free the socket.
Since isotp_release() had already removed itself from the isotp
notifier list at that point, isotp_notify() would never get a chance to
clean up either, leaving a stale CAN filter that keeps pointing at the
freed socket.&lt;/p&gt;
&lt;p&gt;Fix this the same way raw.c already does: hold a tracked reference to
the bound net_device in the socket (so-&amp;gt;dev/so-&amp;gt;dev_tracker) from
bind() onward instead of re-resolving it from the ifindex, and
serialize bind()/release() with rtnl_lock() so that so-&amp;gt;dev is always
consistent with what the NETDEV_UNREGISTER notifier sees. so-&amp;gt;dev
stays valid regardless of ifindex-hash unlisting, and is only ever
cleared by whichever of isotp_release()/isotp_notify() gets there
first, so the filter is always removed exactly once.&lt;/p&gt;
&lt;p&gt;isotp_bind() now rejects a (re)bind with -EAGAIN while so-&amp;gt;[tx|rx].state
isn&amp;#39;t ISOTP_IDLE yet, so a timer left running by a prior
NETDEV_UNREGISTER can&amp;#39;t act on a newly bound so-&amp;gt;ifindex. Both checks
share the same lock_sock() section, so there is no window in whi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-37fw-xv85-q5fg</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72125</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72125</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER isotp_release() looked up the bound network device via dev_get_by_index() using the stored ifindex. During device unregistration the device is unlisted from the ifindex hash before the NETDEV_UNREGISTER notifier chain runs, so a concurrent isotp_release() could find no device, skip can_rx_unregister() entirely, and still proceed to free the socket. Since isotp_release() had already removed itself from the isotp notifier list at that point, isotp_notify() would never get a chance to clean up either, leaving a stale CAN filter that keeps pointing at the freed socket. Fix this the same way raw.c already does: hold a tracked reference to the bound net_device in the socket (so-&amp;gt;dev/so-&amp;gt;dev_tracker) from bind() onward instead of re-resolving it from the ifindex, and serialize bind()/release() with rtnl_lock() so that so-&amp;gt;dev is always consistent with what the NETDEV_UNREGISTER notifier sees. so-&amp;gt;dev stays valid regardless of ifindex-hash unlisting, and is only ever cleared by whichever of isotp_release()/isotp_notify() gets there first, so the filter is always removed exactly once. isotp_bind() now rejects a (re)bind with -EAGAIN while so-&amp;gt;[tx|rx].state isn&amp;#39;t ISOTP_IDLE yet, so a timer left running by a prior NETDEV_UNREGISTER can&amp;#39;t act on a newly bound so-&amp;gt;ifindex. Both checks share the same lock_sock() section, so there is no window in which a…&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER isotp_release() looked up the bound network device via dev_get_by_index() using the stored ifindex. During device unregistration the device is unlisted from the ifindex hash before the NETDEV_UNREGISTER notifier chain runs, so a concurrent isotp_release() could find no device, skip can_rx_unregister() entirely, and still proceed to free the socket. Since isotp_release() had already removed itself from the isotp notifier list at that point, isotp_notify() would never get a chance to clean up either, leaving a stale CAN filter that keeps pointing at the freed socket. Fix this the same way raw.c already does: hold a tracked reference to the bound net_device in the socket (so-&amp;gt;dev/so-&amp;gt;dev_tracker) from bind() onward instead of re-resolving it from the ifindex, and serialize bind()/release() with rtnl_lock() so that so-&amp;gt;dev is always consistent with what the NETDEV_UNREGISTER notifier sees. so-&amp;gt;dev stays valid regardless of ifindex-hash unlisting, and is only ever cleared by whichever of isotp_release()/isotp_notify() gets there first, so the filter is always removed exactly once. isotp_bind() now rejects a (re)bind with -EAGAIN while so-&amp;gt;[tx|rx].state isn&amp;#39;t ISOTP_IDLE yet, so a timer left running by a prior NETDEV_UNREGISTER can&amp;#39;t act on a newly bound so-&amp;gt;ifindex. Both checks share the same lock_sock() section, so there is no window in which a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72125</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
