<?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://cve.radiocsirt.org</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, 03 Oct 2026 16:52:51 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12330</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12330</link>
      <description>bdu:2026-12330</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12330</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23357</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-23357</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://cve.radiocsirt.org/vuln/bell-cve-2026-23357</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0376 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0376</link>
      <description>certfr-2026-avi-0376</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0376</guid>
    </item>
    <item>
      <title>EUVD-2026-315498</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315498</link>
      <description>EUVD-2026-315498</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315498</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23357</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23357</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: mcp251x: fix deadlock in error path of mcp251x_open&lt;/p&gt;
&lt;p&gt;The mcp251x_open() function call free_irq() in its error path with the
mpc_lock mutex held. But if an interrupt already occurred the
interrupt handler will be waiting for the mpc_lock and free_irq() will
deadlock waiting for the handler to finish.&lt;/p&gt;
&lt;p&gt;This issue is similar to the one fixed in commit 7dd9c26bd6cf (&amp;#34;can:
mcp251x: fix deadlock if an interrupt occurs during mcp251x_open&amp;#34;) but
for the error path.&lt;/p&gt;
&lt;p&gt;To solve this issue move the call to free_irq() after the lock is
released. Setting `priv-&amp;gt;force_quit = 1` beforehand ensure that the IRQ
handler will exit right away once it acquired the lock.&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: mcp251x: fix deadlock in error path of mcp251x_open&lt;/p&gt;
&lt;p&gt;The mcp251x_open() function call free_irq() in its error path with the
mpc_lock mutex held. But if an interrupt already occurred the
interrupt handler will be waiting for the mpc_lock and free_irq() will
deadlock waiting for the handler to finish.&lt;/p&gt;
&lt;p&gt;This issue is similar to the one fixed in commit 7dd9c26bd6cf (&amp;#34;can:
mcp251x: fix deadlock if an interrupt occurs during mcp251x_open&amp;#34;) but
for the error path.&lt;/p&gt;
&lt;p&gt;To solve this issue move the call to free_irq() after the lock is
released. Setting `priv-&amp;gt;force_quit = 1` beforehand ensure that the IRQ
handler will exit right away once it acquired the lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23357</guid>
    </item>
    <item>
      <title>GHSA-f94p-fcww-cpfj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f94p-fcww-cpfj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: mcp251x: fix deadlock in error path of mcp251x_open&lt;/p&gt;
&lt;p&gt;The mcp251x_open() function call free_irq() in its error path with the
mpc_lock mutex held. But if an interrupt already occurred the
interrupt handler will be waiting for the mpc_lock and free_irq() will
deadlock waiting for the handler to finish.&lt;/p&gt;
&lt;p&gt;This issue is similar to the one fixed in commit 7dd9c26bd6cf (&amp;#34;can:
mcp251x: fix deadlock if an interrupt occurs during mcp251x_open&amp;#34;) but
for the error path.&lt;/p&gt;
&lt;p&gt;To solve this issue move the call to free_irq() after the lock is
released. Setting `priv-&amp;gt;force_quit = 1` beforehand ensure that the IRQ
handler will exit right away once it acquired the lock.&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: mcp251x: fix deadlock in error path of mcp251x_open&lt;/p&gt;
&lt;p&gt;The mcp251x_open() function call free_irq() in its error path with the
mpc_lock mutex held. But if an interrupt already occurred the
interrupt handler will be waiting for the mpc_lock and free_irq() will
deadlock waiting for the handler to finish.&lt;/p&gt;
&lt;p&gt;This issue is similar to the one fixed in commit 7dd9c26bd6cf (&amp;#34;can:
mcp251x: fix deadlock if an interrupt occurs during mcp251x_open&amp;#34;) but
for the error path.&lt;/p&gt;
&lt;p&gt;To solve this issue move the call to free_irq() after the lock is
released. Setting `priv-&amp;gt;force_quit = 1` beforehand ensure that the IRQ
handler will exit right away once it acquired the lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f94p-fcww-cpfj</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-23357 — can: mcp251x: fix deadlock in error path of mcp251x_open</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-23357</link>
      <description>msrc_CVE-2026-23357</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-23357</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20826-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:21834-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:21834-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:21834-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23357</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23357</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 232 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: mcp251x: fix deadlock in error path of mcp251x_open The mcp251x_open() function call free_irq() in its error path with the mpc_lock mutex held. But if an interrupt already occurred the interrupt handler will be waiting for the mpc_lock and free_irq() will deadlock waiting for the handler to finish. This issue is similar to the one fixed in commit 7dd9c26bd6cf (&amp;#34;can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open&amp;#34;) but for the error path. To solve this issue move the call to free_irq() after the lock is released. Setting `priv-&amp;gt;force_quit = 1` beforehand ensure that the IRQ handler will exit right away once it acquired the lock.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 232 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: mcp251x: fix deadlock in error path of mcp251x_open The mcp251x_open() function call free_irq() in its error path with the mpc_lock mutex held. But if an interrupt already occurred the interrupt handler will be waiting for the mpc_lock and free_irq() will deadlock waiting for the handler to finish. This issue is similar to the one fixed in commit 7dd9c26bd6cf (&amp;#34;can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open&amp;#34;) but for the error path. To solve this issue move the call to free_irq() after the lock is released. Setting `priv-&amp;gt;force_quit = 1` beforehand ensure that the IRQ handler will exit right away once it acquired the lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23357</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0861 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0861</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0861</guid>
    </item>
  </channel>
</rss>
