<?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-10-07T05:35:51.410880+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/fkie_cve-2026-98343</id>
    <title>fkie_cve-2026-98343</title>
    <updated>2026-10-07T05:35:51.413876+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>dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel()</p>
<p>When dma_device_put() drops the last reference on chan-&gt;device-&gt;ref,
dma_device_release() runs and may free the dma_device along with its
channels.</p>
<p>dma_chan_put() then still reads chan-&gt;device-&gt;owner via
dma_chan_to_owner() for the trailing module_put(). KASAN catches it:</p>
<p>slab-use-after-free in dma_chan_put+0x3e6/0x4c0
	Read of size 8 by task insmod/6319
	Freed by task 6319:
	  kfree+0x225/0x470
	  dma_chan_put+0x395/0x4c0
	  dmaengine_put+0xf8/0x160</p>
<p>Cache the module owner in dma_chan_put() before the put so the trailing
module_put() does not need chan-&gt;device.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-98343"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-rw66-9h9x-4vjf</id>
    <title>GHSA-rw66-9h9x-4vjf</title>
    <updated>2026-10-07T05:35:51.414006+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>dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel()</p>
<p>When dma_device_put() drops the last reference on chan-&gt;device-&gt;ref,
dma_device_release() runs and may free the dma_device along with its
channels.</p>
<p>dma_chan_put() then still reads chan-&gt;device-&gt;owner via
dma_chan_to_owner() for the trailing module_put(). KASAN catches it:</p>
<p>slab-use-after-free in dma_chan_put+0x3e6/0x4c0
	Read of size 8 by task insmod/6319
	Freed by task 6319:
	  kfree+0x225/0x470
	  dma_chan_put+0x395/0x4c0
	  dmaengine_put+0xf8/0x160</p>
<p>Cache the module owner in dma_chan_put() before the put so the trailing
module_put() does not need chan-&gt;device.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-rw66-9h9x-4vjf"/>
  </entry>
</feed>
