<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T07:37:32.496459+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-43061</id>
    <title>CVE-2026-43061 — serial: 8250: Fix TX deadlock when using DMA</title>
    <updated>2026-09-28T07:37:32.508974+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>serial: 8250: Fix TX deadlock when using DMA</p>
<p>`dmaengine_terminate_async` does not guarantee that the
`__dma_tx_complete` callback will run. The callback is currently the
only place where `dma-&gt;tx_running` gets cleared. If the transaction is
canceled and the callback never runs, then `dma-&gt;tx_running` will never
get cleared and we will never schedule new TX DMA transactions again.</p>
<p>This change makes it so we clear `dma-&gt;tx_running` after we terminate
the DMA transaction. This is "safe" because `serial8250_tx_dma_flush`
is holding the UART port lock. The first thing the callback does is also
grab the UART port lock, so access to `dma-&gt;tx_running` is serialized.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-43061"/>
  </entry>
</feed>
