<?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>Mon, 28 Sep 2026 06:37:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72138 — xen/gntdev: fix error handling in ioctl</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72138</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/gntdev: fix error handling in ioctl&lt;/p&gt;
&lt;p&gt;When gntdev_ioctl_map_grant_ref() fails to copy the operation result
back to userspace after successfully adding the mapping to the list,
the error path returns -EFAULT without releasing the reference
acquired by gntdev_alloc_map(). The mapping remains in priv-&amp;gt;maps
with a refcount of 1, causing a memory leak and a dangling list
entry.&lt;/p&gt;
&lt;p&gt;Additionally, gntdev_add_map() may modify map-&amp;gt;index to avoid overlap
with existing mappings. Therefore, the index returned to userspace
must be obtained after gntdev_add_map() completes.&lt;/p&gt;
&lt;p&gt;Fix this by holding the mutex across gntdev_add_map(), retrieving
the correct index, and copy_to_user(). If copy_to_user() fails,
remove the mapping from the list and release the reference while
still holding the lock.&lt;/p&gt;
&lt;p&gt;Fix these issues by properly handling all error cases.&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/gntdev: fix error handling in ioctl&lt;/p&gt;
&lt;p&gt;When gntdev_ioctl_map_grant_ref() fails to copy the operation result
back to userspace after successfully adding the mapping to the list,
the error path returns -EFAULT without releasing the reference
acquired by gntdev_alloc_map(). The mapping remains in priv-&amp;gt;maps
with a refcount of 1, causing a memory leak and a dangling list
entry.&lt;/p&gt;
&lt;p&gt;Additionally, gntdev_add_map() may modify map-&amp;gt;index to avoid overlap
with existing mappings. Therefore, the index returned to userspace
must be obtained after gntdev_add_map() completes.&lt;/p&gt;
&lt;p&gt;Fix this by holding the mutex across gntdev_add_map(), retrieving
the correct index, and copy_to_user(). If copy_to_user() fails,
remove the mapping from the list and release the reference while
still holding the lock.&lt;/p&gt;
&lt;p&gt;Fix these issues by properly handling all error cases.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72138</guid>
    </item>
  </channel>
</rss>
