<?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://vulnerability.circl.lu</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>Sat, 03 Oct 2026 21:38:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38595 — xen: fix UAF in dmabuf_exp_from_pages()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38595</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;xen: fix UAF in dmabuf_exp_from_pages()&lt;/p&gt;
&lt;p&gt;[dma_buf_fd() fixes; no preferences regarding the tree it goes through -
up to xen folks]&lt;/p&gt;
&lt;p&gt;As soon as we&amp;#39;d inserted a file reference into descriptor table, another
thread could close it.  That&amp;#39;s fine for the case when all we are doing is
returning that descriptor to userland (it&amp;#39;s a race, but it&amp;#39;s a userland
race and there&amp;#39;s nothing the kernel can do about it).  However, if we
follow fd_install() with any kind of access to objects that would be
destroyed on close (be it the struct file itself or anything destroyed
by its -&amp;gt;release()), we have a UAF.&lt;/p&gt;
&lt;p&gt;dma_buf_fd() is a combination of reserving a descriptor and fd_install().
gntdev dmabuf_exp_from_pages() calls it and then proceeds to access the
objects destroyed on close - starting with gntdev_dmabuf itself.&lt;/p&gt;
&lt;p&gt;Fix that by doing reserving descriptor before anything else and do
fd_install() only when everything had been set up.&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;xen: fix UAF in dmabuf_exp_from_pages()&lt;/p&gt;
&lt;p&gt;[dma_buf_fd() fixes; no preferences regarding the tree it goes through -
up to xen folks]&lt;/p&gt;
&lt;p&gt;As soon as we&amp;#39;d inserted a file reference into descriptor table, another
thread could close it.  That&amp;#39;s fine for the case when all we are doing is
returning that descriptor to userland (it&amp;#39;s a race, but it&amp;#39;s a userland
race and there&amp;#39;s nothing the kernel can do about it).  However, if we
follow fd_install() with any kind of access to objects that would be
destroyed on close (be it the struct file itself or anything destroyed
by its -&amp;gt;release()), we have a UAF.&lt;/p&gt;
&lt;p&gt;dma_buf_fd() is a combination of reserving a descriptor and fd_install().
gntdev dmabuf_exp_from_pages() calls it and then proceeds to access the
objects destroyed on close - starting with gntdev_dmabuf itself.&lt;/p&gt;
&lt;p&gt;Fix that by doing reserving descriptor before anything else and do
fd_install() only when everything had been set up.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38595</guid>
    </item>
  </channel>
</rss>
