<?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>Fri, 02 Oct 2026 00:07:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64591 — iommu/vt-d: Avoid WARNING in sva unbind path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64591</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/vt-d: Avoid WARNING in sva unbind path&lt;/p&gt;
&lt;p&gt;The Intel IOMMU driver allows SVA on devices even if they do not support
PCI/PRI. Commit 39c20c4e83b9 (&amp;#34;iommu/vt-d: Only handle IOPF for SVA when
PRI is supported&amp;#34;) modified the SVA bind path to allow this configuration
by skipping IOPF enablement when PRI is missing. However, it failed to
update the unbind path.&lt;/p&gt;
&lt;p&gt;This creates an imbalance: the unbind path attempts to disable IOPF for
a device that never had it enabled, triggering a WARNING in
intel_iommu_disable_iopf():&lt;/p&gt;
&lt;p&gt;WARNING: drivers/iommu/intel/iommu.c:3475 at intel_iommu_disable_iopf+0x4f/0x90d
 Call Trace:
  &amp;lt;TASK&amp;gt;
  blocking_domain_set_dev_pasid+0x50/0x70
  iommu_detach_device_pasid+0x89/0xc0
  iommu_sva_unbind_device+0x73/0x150
  xe_vm_close_and_put+0x4d2/0x1200 [xe]&lt;/p&gt;
&lt;p&gt;Fix this by bypassing IOPF operations for SVA domains on non-PRI hardware
in both the bind and unbind paths.&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/vt-d: Avoid WARNING in sva unbind path&lt;/p&gt;
&lt;p&gt;The Intel IOMMU driver allows SVA on devices even if they do not support
PCI/PRI. Commit 39c20c4e83b9 (&amp;#34;iommu/vt-d: Only handle IOPF for SVA when
PRI is supported&amp;#34;) modified the SVA bind path to allow this configuration
by skipping IOPF enablement when PRI is missing. However, it failed to
update the unbind path.&lt;/p&gt;
&lt;p&gt;This creates an imbalance: the unbind path attempts to disable IOPF for
a device that never had it enabled, triggering a WARNING in
intel_iommu_disable_iopf():&lt;/p&gt;
&lt;p&gt;WARNING: drivers/iommu/intel/iommu.c:3475 at intel_iommu_disable_iopf+0x4f/0x90d
 Call Trace:
  &amp;lt;TASK&amp;gt;
  blocking_domain_set_dev_pasid+0x50/0x70
  iommu_detach_device_pasid+0x89/0xc0
  iommu_sva_unbind_device+0x73/0x150
  xe_vm_close_and_put+0x4d2/0x1200 [xe]&lt;/p&gt;
&lt;p&gt;Fix this by bypassing IOPF operations for SVA domains on non-PRI hardware
in both the bind and unbind paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64591</guid>
    </item>
  </channel>
</rss>
