<?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>Tue, 29 Sep 2026 19:16:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21770 — iommu: Fix potential memory leak in iopf_queue_remove_device()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21770</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;iommu: Fix potential memory leak in iopf_queue_remove_device()&lt;/p&gt;
&lt;p&gt;The iopf_queue_remove_device() helper removes a device from the per-iommu
iopf queue when PRI is disabled on the device. It responds to all
outstanding iopf&amp;#39;s with an IOMMU_PAGE_RESP_INVALID code and detaches the
device from the queue.&lt;/p&gt;
&lt;p&gt;However, it fails to release the group structure that represents a group
of iopf&amp;#39;s awaiting for a response after responding to the hardware. This
can cause a memory leak if iopf_queue_remove_device() is called with
pending iopf&amp;#39;s.&lt;/p&gt;
&lt;p&gt;Fix it by calling iopf_free_group() after the iopf group is responded.&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;iommu: Fix potential memory leak in iopf_queue_remove_device()&lt;/p&gt;
&lt;p&gt;The iopf_queue_remove_device() helper removes a device from the per-iommu
iopf queue when PRI is disabled on the device. It responds to all
outstanding iopf&amp;#39;s with an IOMMU_PAGE_RESP_INVALID code and detaches the
device from the queue.&lt;/p&gt;
&lt;p&gt;However, it fails to release the group structure that represents a group
of iopf&amp;#39;s awaiting for a response after responding to the hardware. This
can cause a memory leak if iopf_queue_remove_device() is called with
pending iopf&amp;#39;s.&lt;/p&gt;
&lt;p&gt;Fix it by calling iopf_free_group() after the iopf group is responded.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21770</guid>
    </item>
  </channel>
</rss>
