<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 11:47:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89447 — iommufd: Avoid locking internal accesses during unmap</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-89447</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;iommufd: Avoid locking internal accesses during unmap&lt;/p&gt;
&lt;p&gt;iommufd_access_notify_unmap() skips internal accesses because they do
not have an external unmap callback to invoke.&lt;/p&gt;
&lt;p&gt;However, the current test calls iommufd_lock_obj() before checking
whether the access is internal. If iommufd_lock_obj() succeeds, the loop
then sees the internal access and continues, bypassing the matching
iommufd_put_object() used by the normal unmap path. This leaks the
object reference taken by iommufd_lock_obj().&lt;/p&gt;
&lt;p&gt;Check for internal accesses first so skipped entries are never locked.&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;iommufd: Avoid locking internal accesses during unmap&lt;/p&gt;
&lt;p&gt;iommufd_access_notify_unmap() skips internal accesses because they do
not have an external unmap callback to invoke.&lt;/p&gt;
&lt;p&gt;However, the current test calls iommufd_lock_obj() before checking
whether the access is internal. If iommufd_lock_obj() succeeds, the loop
then sees the internal access and continues, bypassing the matching
iommufd_put_object() used by the normal unmap path. This leaks the
object reference taken by iommufd_lock_obj().&lt;/p&gt;
&lt;p&gt;Check for internal accesses first so skipped entries are never locked.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-89447</guid>
    </item>
  </channel>
</rss>
