Linux Kernel up to 6.18.38/7.1.3 Intel IOMMU driver iommu.c intel_iommu_disable_iopf locking

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.7$0-$5k0.60

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.18.38/7.1.3. It has been rated as problematic. The affected element is the function intel_iommu_disable_iopf of the file drivers/iommu/intel/iommu.c of the component Intel IOMMU driver. This manipulation causes locking. This vulnerability is handled as CVE-2026-64591. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.18.38/7.1.3 and classified as problematic. Affected by this vulnerability is the function intel_iommu_disable_iopf of the file drivers/iommu/intel/iommu.c of the component Intel IOMMU driver. The manipulation with an unknown input leads to a locking vulnerability. The CWE definition for the vulnerability is CWE-667. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. As an impact it is known to affect availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-64591 since 07/19/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation needs additional levels of successful authentication. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 6.18.39, 7.1.4 or 7.2-rc1 eliminates this vulnerability. Applying the patch bb354384f40bb087e7c44f0f0743a23fc945f91d/477f8dec3b5ae54e8ef3c33bdd2257e47896512e/534b5f98ab7319d8004bbc7dab6481462243e883 is able to eliminate this problem.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.9
VulDB Meta Temp Score: 4.7

VulDB Base Score: 4.9
VulDB Temp Score: 4.7
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Locking
CWE: CWE-667
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.18.39/7.1.4/7.2-rc1
Patch: bb354384f40bb087e7c44f0f0743a23fc945f91d/477f8dec3b5ae54e8ef3c33bdd2257e47896512e/534b5f98ab7319d8004bbc7dab6481462243e883

Timelineinfo

07/19/2026 CVE reserved
08/06/2026 +18 days Advisory disclosed
08/06/2026 +0 days VulDB entry created
08/06/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64591 (🔒)
GCVE (CVE): GCVE-0-2026-64591
GCVE (VulDB): GCVE-100-386491

Entryinfo

Created: 08/06/2026 09:38
Changes: 08/06/2026 09:38 (60)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!