<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-26T17:35:35.760888+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-98903</id>
    <title>fkie_cve-2026-98903</title>
    <updated>2026-10-26T17:35:35.787934+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mailbox: imx: Add a channel shutdown field</p>
<p>sashiko complained about possible teardown problem. The scenario</p>
<p>CPU 0                              CPU 1
  imx_mu_isr()                   imx_mu_shutdown()
                                   imx_mu_xcr_rmw(priv, IMX_MU_RCR, 0, IMX_MU_xCR_RIEn(priv-&gt;dcfg-&gt;type, cp-&gt;idx));
    imx_mu_specific_rx()
      imx_mu_xcr_rmw(priv, IMX_MU_RCR, IMX_MU_xCR_RIEn(priv-&gt;dcfg-&gt;type, 0), 0);
                                   free_irq()</p>
<p>The RX event remains enabled because in this short window the RX event
was disabled in -&gt;shutdown() while the interrupt was active and then
enabled again by the ISR while -&gt;shutdown waited in free_irq().</p>
<p>This race requires timing and if happens can be problematic on shared
handlers if the "removed" channel triggers an interrupt. In this case
the irq-core will shutdown the interrupt with the "nobody cared"
message.</p>
<p>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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-98903"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-6pc9-8xrq-jmj4</id>
    <title>GHSA-6pc9-8xrq-jmj4</title>
    <updated>2026-10-26T17:35:35.788026+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mailbox: imx: Add a channel shutdown field</p>
<p>sashiko complained about possible teardown problem. The scenario</p>
<p>CPU 0                              CPU 1
  imx_mu_isr()                   imx_mu_shutdown()
                                   imx_mu_xcr_rmw(priv, IMX_MU_RCR, 0, IMX_MU_xCR_RIEn(priv-&gt;dcfg-&gt;type, cp-&gt;idx));
    imx_mu_specific_rx()
      imx_mu_xcr_rmw(priv, IMX_MU_RCR, IMX_MU_xCR_RIEn(priv-&gt;dcfg-&gt;type, 0), 0);
                                   free_irq()</p>
<p>The RX event remains enabled because in this short window the RX event
was disabled in -&gt;shutdown() while the interrupt was active and then
enabled again by the ISR while -&gt;shutdown waited in free_irq().</p>
<p>This race requires timing and if happens can be problematic on shared
handlers if the "removed" channel triggers an interrupt. In this case
the irq-core will shutdown the interrupt with the "nobody cared"
message.</p>
<p>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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-6pc9-8xrq-jmj4"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-98903</id>
    <title>msrc_CVE-2026-98903 — mailbox: imx: Add a channel shutdown field</title>
    <updated>2026-10-26T17:35:35.788060+00:00</updated>
    <content>msrc_CVE-2026-98903</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-98903"/>
  </entry>
</feed>
