<?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://db.gcve.eu</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, 20 Nov 2026 21:18:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99447 — spi: spi-pci1xxxx: quiesce DMA engines on transfer timeout</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99447</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;spi: spi-pci1xxxx: quiesce DMA engines on transfer timeout&lt;/p&gt;
&lt;p&gt;If a DMA-mapped transfer times out waiting for DMA_TERM and neither DMA
abort interrupt arrived, pci1xxxx_spi_transfer_with_dma() returns
through the error label while both DMA engines are still enabled, the
done/abort interrupt status is still armed and the transfer state
(p-&amp;gt;xfer, p-&amp;gt;tx_sgl, p-&amp;gt;rx_sgl) is still registered.&lt;/p&gt;
&lt;p&gt;The ISRs keep firing afterwards: they reprogram the DMA engines from
p-&amp;gt;tx_sgl / p-&amp;gt;rx_sgl and signal completion through p-&amp;gt;xfer and
p-&amp;gt;spi_xfer_done, all of which the SPI core is free to unmap or reuse
once transfer_one() has returned, which is a use-after-free. A late
done interrupt can also start the next transfer queued behind the
failed one.&lt;/p&gt;
&lt;p&gt;Stop both DMA engines, drain the pending done/abort interrupt status
and synchronize the DMA IRQs before dropping the in-progress state and
the transfer pointers, and re-enable the engines afterwards so that
subsequent transfers keep working. The engines are only turned back on
once both were confirmed to have stopped: re-enabling an engine that
failed to stop would cancel the pending stop request and let it keep
running into buffers the SPI core is about to unmap or free, which is
exactly the window this patch closes. An engine that failed to stop is
left disabled, as the abort paths already do.&lt;/p&gt;
&lt;p&gt;The DMA interrupt status and mask registers are shared between the two
SPI instances, s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;spi: spi-pci1xxxx: quiesce DMA engines on transfer timeout&lt;/p&gt;
&lt;p&gt;If a DMA-mapped transfer times out waiting for DMA_TERM and neither DMA
abort interrupt arrived, pci1xxxx_spi_transfer_with_dma() returns
through the error label while both DMA engines are still enabled, the
done/abort interrupt status is still armed and the transfer state
(p-&amp;gt;xfer, p-&amp;gt;tx_sgl, p-&amp;gt;rx_sgl) is still registered.&lt;/p&gt;
&lt;p&gt;The ISRs keep firing afterwards: they reprogram the DMA engines from
p-&amp;gt;tx_sgl / p-&amp;gt;rx_sgl and signal completion through p-&amp;gt;xfer and
p-&amp;gt;spi_xfer_done, all of which the SPI core is free to unmap or reuse
once transfer_one() has returned, which is a use-after-free. A late
done interrupt can also start the next transfer queued behind the
failed one.&lt;/p&gt;
&lt;p&gt;Stop both DMA engines, drain the pending done/abort interrupt status
and synchronize the DMA IRQs before dropping the in-progress state and
the transfer pointers, and re-enable the engines afterwards so that
subsequent transfers keep working. The engines are only turned back on
once both were confirmed to have stopped: re-enabling an engine that
failed to stop would cancel the pending stop request and let it keep
running into buffers the SPI core is about to unmap or free, which is
exactly the window this patch closes. An engine that failed to stop is
left disabled, as the abort paths already do.&lt;/p&gt;
&lt;p&gt;The DMA interrupt status and mask registers are shared between the two
SPI instances, s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99447</guid>
    </item>
  </channel>
</rss>
