Answer in brief
CVE-2026-64591 records a Unknown severity vulnerability in iommu/vt-d: Avoid WARNING in sva unbind path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ee312bb1052e45cbccaf6abac1012db9ca43150a <bb354384f40bb087e7c44f0f0743a23fc945f91d || >=39c20c4e83b9f78988541d829aa34668904e54a0 <477f8dec3b5ae54e8ef3c33bdd2257e47896512e || >=39c20c4e83b9f78988541d829aa34668904e54a0 <534b5f98ab7319d8004bbc7dab6481462243e883 || 46461dabb95239aa05e31e247cd21151b8406642 || >=6.18.20 <6.18.39 || >=6.19.10 <6.20 | bb354384f40bb087e7c44f0f0743a23fc945f91d, 477f8dec3b5ae54e8ef3c33bdd2257e47896512e, 534b5f98ab7319d8004bbc7dab6481462243e883, 6.18.39, 6.20 |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64591 records a Unknown severity vulnerability in iommu/vt-d: Avoid WARNING in sva unbind path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ee312bb1052e45cbccaf6abac1012db9ca43150a <bb354384f40bb087e7c44f0f0743a23fc945f91d || >=39c20c4e83b9f78988541d829aa34668904e54a0 <477f8dec3b5ae54e8ef3c33bdd2257e47896512e || >=39c20c4e83b9f78988541d829aa34668904e54a0 <534b5f98ab7319d8004bbc7dab6481462243e883 || 46461dabb95239aa05e31e247cd21151b8406642 || >=6.18.20 <6.18.39 || >=6.19.10 <6.20 | bb354384f40bb087e7c44f0f0743a23fc945f91d, 477f8dec3b5ae54e8ef3c33bdd2257e47896512e, 534b5f98ab7319d8004bbc7dab6481462243e883, 6.18.39, 6.20 |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.