Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 11 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ee312bb1052e45cbccaf6abac1012db9ca43150a – < bb354384f40bb087e7c44f0f0743a23fc945f91d
    • affected 39c20c4e83b9f78988541d829aa34668904e54a0 – < 477f8dec3b5ae54e8ef3c33bdd2257e47896512e
    • affected 39c20c4e83b9f78988541d829aa34668904e54a0 – < 534b5f98ab7319d8004bbc7dab6481462243e883
    • affected 46461dabb95239aa05e31e247cd21151b8406642
    • affected 6.18.20 – < 6.18.39
    • affected 6.19.10 – < 6.20
  • Linux · Linux

    • affected 7.0
    • unaffected < 7.0
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64591 badge
[![CVE-2026-64591](https://cveledger.app/badge/CVE-2026-64591.svg)](https://cveledger.app/cve/CVE-2026-64591)

Record last updated .