<?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>Tue, 17 Nov 2026 10:10:07 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98903</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98903</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-98903</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1469 — 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://cve.radiocsirt.org/vuln/certfr-2026-avi-1469</link>
      <description>certfr-2026-avi-1469</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1469</guid>
    </item>
    <item>
      <title>EUVD-2026-392170</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-392170</link>
      <description>EUVD-2026-392170</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-392170</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98903</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98903</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mailbox: imx: Add a channel shutdown field&lt;/p&gt;
&lt;p&gt;sashiko complained about possible teardown problem. The scenario&lt;/p&gt;
&lt;p&gt;CPU 0                              CPU 1
  imx_mu_isr()                   imx_mu_shutdown()
                                   imx_mu_xcr_rmw(priv, IMX_MU_RCR, 0, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, cp-&amp;gt;idx));
    imx_mu_specific_rx()
      imx_mu_xcr_rmw(priv, IMX_MU_RCR, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, 0), 0);
                                   free_irq()&lt;/p&gt;
&lt;p&gt;The RX event remains enabled because in this short window the RX event
was disabled in -&amp;gt;shutdown() while the interrupt was active and then
enabled again by the ISR while -&amp;gt;shutdown waited in free_irq().&lt;/p&gt;
&lt;p&gt;This race requires timing and if happens can be problematic on shared
handlers if the &amp;#34;removed&amp;#34; channel triggers an interrupt. In this case
the irq-core will shutdown the interrupt with the &amp;#34;nobody cared&amp;#34;
message.&lt;/p&gt;
&lt;p&gt;Introduce imx_mu_con_priv::shutdown to signal that the channel is
shutting down. This flag is set with the lock held (by
imx_mu_xcr_clr_shut()). The unmask side uses imx_mu_xcr_set_act() which
only enables the event if the channel has not been shutdown and
serialises on the same 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;mailbox: imx: Add a channel shutdown field&lt;/p&gt;
&lt;p&gt;sashiko complained about possible teardown problem. The scenario&lt;/p&gt;
&lt;p&gt;CPU 0                              CPU 1
  imx_mu_isr()                   imx_mu_shutdown()
                                   imx_mu_xcr_rmw(priv, IMX_MU_RCR, 0, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, cp-&amp;gt;idx));
    imx_mu_specific_rx()
      imx_mu_xcr_rmw(priv, IMX_MU_RCR, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, 0), 0);
                                   free_irq()&lt;/p&gt;
&lt;p&gt;The RX event remains enabled because in this short window the RX event
was disabled in -&amp;gt;shutdown() while the interrupt was active and then
enabled again by the ISR while -&amp;gt;shutdown waited in free_irq().&lt;/p&gt;
&lt;p&gt;This race requires timing and if happens can be problematic on shared
handlers if the &amp;#34;removed&amp;#34; channel triggers an interrupt. In this case
the irq-core will shutdown the interrupt with the &amp;#34;nobody cared&amp;#34;
message.&lt;/p&gt;
&lt;p&gt;Introduce imx_mu_con_priv::shutdown to signal that the channel is
shutting down. This flag is set with the lock held (by
imx_mu_xcr_clr_shut()). The unmask side uses imx_mu_xcr_set_act() which
only enables the event if the channel has not been shutdown and
serialises on the same lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98903</guid>
    </item>
    <item>
      <title>GHSA-6pc9-8xrq-jmj4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6pc9-8xrq-jmj4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mailbox: imx: Add a channel shutdown field&lt;/p&gt;
&lt;p&gt;sashiko complained about possible teardown problem. The scenario&lt;/p&gt;
&lt;p&gt;CPU 0                              CPU 1
  imx_mu_isr()                   imx_mu_shutdown()
                                   imx_mu_xcr_rmw(priv, IMX_MU_RCR, 0, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, cp-&amp;gt;idx));
    imx_mu_specific_rx()
      imx_mu_xcr_rmw(priv, IMX_MU_RCR, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, 0), 0);
                                   free_irq()&lt;/p&gt;
&lt;p&gt;The RX event remains enabled because in this short window the RX event
was disabled in -&amp;gt;shutdown() while the interrupt was active and then
enabled again by the ISR while -&amp;gt;shutdown waited in free_irq().&lt;/p&gt;
&lt;p&gt;This race requires timing and if happens can be problematic on shared
handlers if the &amp;#34;removed&amp;#34; channel triggers an interrupt. In this case
the irq-core will shutdown the interrupt with the &amp;#34;nobody cared&amp;#34;
message.&lt;/p&gt;
&lt;p&gt;Introduce imx_mu_con_priv::shutdown to signal that the channel is
shutting down. This flag is set with the lock held (by
imx_mu_xcr_clr_shut()). The unmask side uses imx_mu_xcr_set_act() which
only enables the event if the channel has not been shutdown and
serialises on the same 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;mailbox: imx: Add a channel shutdown field&lt;/p&gt;
&lt;p&gt;sashiko complained about possible teardown problem. The scenario&lt;/p&gt;
&lt;p&gt;CPU 0                              CPU 1
  imx_mu_isr()                   imx_mu_shutdown()
                                   imx_mu_xcr_rmw(priv, IMX_MU_RCR, 0, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, cp-&amp;gt;idx));
    imx_mu_specific_rx()
      imx_mu_xcr_rmw(priv, IMX_MU_RCR, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, 0), 0);
                                   free_irq()&lt;/p&gt;
&lt;p&gt;The RX event remains enabled because in this short window the RX event
was disabled in -&amp;gt;shutdown() while the interrupt was active and then
enabled again by the ISR while -&amp;gt;shutdown waited in free_irq().&lt;/p&gt;
&lt;p&gt;This race requires timing and if happens can be problematic on shared
handlers if the &amp;#34;removed&amp;#34; channel triggers an interrupt. In this case
the irq-core will shutdown the interrupt with the &amp;#34;nobody cared&amp;#34;
message.&lt;/p&gt;
&lt;p&gt;Introduce imx_mu_con_priv::shutdown to signal that the channel is
shutting down. This flag is set with the lock held (by
imx_mu_xcr_clr_shut()). The unmask side uses imx_mu_xcr_set_act() which
only enables the event if the channel has not been shutdown and
serialises on the same lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6pc9-8xrq-jmj4</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98903 — mailbox: imx: Add a channel shutdown field</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98903</link>
      <description>msrc_CVE-2026-98903</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98903</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98903</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98903</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 197 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mailbox: imx: Add a channel shutdown field sashiko complained about possible teardown problem. The scenario  CPU 0                              CPU 1   imx_mu_isr()                   imx_mu_shutdown()                                    imx_mu_xcr_rmw(priv, IMX_MU_RCR, 0, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, cp-&amp;gt;idx));     imx_mu_specific_rx()       imx_mu_xcr_rmw(priv, IMX_MU_RCR, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, 0), 0);                                    free_irq() The RX event remains enabled because in this short window the RX event was disabled in -&amp;gt;shutdown() while the interrupt was active and then enabled again by the ISR while -&amp;gt;shutdown waited in free_irq(). This race requires timing and if happens can be problematic on shared handlers if the &amp;#34;removed&amp;#34; channel triggers an interrupt. In this case the irq-core will shutdown the interrupt with the &amp;#34;nobody cared&amp;#34; message. Introduce imx_mu_con_priv::shutdown to signal that the channel is shutting down. This flag is set with the lock held (by imx_mu_xcr_clr_shut()). The unmask side uses imx_mu_xcr_set_act() which only enables the event if the channel has not been shutdown and serialises on the same lock.&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 197 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mailbox: imx: Add a channel shutdown field sashiko complained about possible teardown problem. The scenario  CPU 0                              CPU 1   imx_mu_isr()                   imx_mu_shutdown()                                    imx_mu_xcr_rmw(priv, IMX_MU_RCR, 0, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, cp-&amp;gt;idx));     imx_mu_specific_rx()       imx_mu_xcr_rmw(priv, IMX_MU_RCR, IMX_MU_xCR_RIEn(priv-&amp;gt;dcfg-&amp;gt;type, 0), 0);                                    free_irq() The RX event remains enabled because in this short window the RX event was disabled in -&amp;gt;shutdown() while the interrupt was active and then enabled again by the ISR while -&amp;gt;shutdown waited in free_irq(). This race requires timing and if happens can be problematic on shared handlers if the &amp;#34;removed&amp;#34; channel triggers an interrupt. In this case the irq-core will shutdown the interrupt with the &amp;#34;nobody cared&amp;#34; message. Introduce imx_mu_con_priv::shutdown to signal that the channel is shutting down. This flag is set with the lock held (by imx_mu_xcr_clr_shut()). The unmask side uses imx_mu_xcr_set_act() which only enables the event if the channel has not been shutdown and serialises on the same lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98903</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
