CVE-2026-64591

iommu/vt-d: Avoid WARNING in sva unbind path

N/A

Published: August 6, 2026 at 07:13 AM UTC

Updated: August 17, 2026 at 05:18 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Avoid WARNING in sva unbind path The Intel IOMMU driver allows SVA on devices even if they do not support PCI/PRI. Commit 39c20c4e83b9 ("iommu/vt-d: Only handle IOPF for SVA when PRI is supported") 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. 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(): WARNING: drivers/iommu/intel/iommu.c:3475 at intel_iommu_disable_iopf+0x4f/0x90d Call Trace: <TASK> 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] Fix this by bypassing IOPF operations for SVA domains on non-PRI hardware in both the bind and unbind paths.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 6.19.106.18.20 ≤ v < 6.18.396.19.10 ≤ v < 6.207.0 ≤ v < 7.1.47.0 ≤ v < 7.239c20c4e83b9f78988541d829aa34668904e54a046461dabb95239aa05e31e247cd21151b84066426.18.20 6.19.10 7.0ee312bb1052e45cbccaf6abac1012db9ca43150a

Vendor states this is fixed in 477f8dec3b5ae54e8ef3c33bdd2257e47896512e (fixed)

Vendor states this is fixed in 534b5f98ab7319d8004bbc7dab6481462243e883 (fixed)

Vendor states this is fixed in bb354384f40bb087e7c44f0f0743a23fc945f91d (fixed)

Vendor states this is fixed in 6.18.39 (unaffected)

Affected range stops below 6.20, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 7.0 (unaffected)

Vendor states this is fixed in 7.1.4 (unaffected)

Vendor states this is fixed in 7.2 (unaffected)