CVE-2026-45894

iommu/vt-d: Clear Present bit before tearing down PASID entry

State
Published
Severity
7.8 High
Published
May 27, 2026
Updated
Oct 30, 2026
Reserved
May 13, 2026

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

iommu/vt-d: Clear Present bit before tearing down PASID entry

The Intel VT-d Scalable Mode PASID table entry consists of 512 bits (64 bytes). When tearing down an entry, the current implementation zeros the entire 64-byte structure immediately using multiple 64-bit writes.

Since the IOMMU hardware may fetch these 64 bytes using multiple internal transactions (e.g., four 128-bit bursts), updating or zeroing the entire entry while it is active (P=1) risks a "torn" read. If a hardware fetch occurs simultaneously with the CPU zeroing the entry, the hardware could observe an inconsistent state, leading to unpredictable behavior or spurious faults.

Follow the "Guidance to Software for Invalidations" in the VT-d spec (Section 6.5.3.3) by implementing the recommended ownership handshake:

1. Clear only the 'Present' (P) bit of the PASID entry. 2. Use a dma_wmb() to ensure the cleared bit is visible to hardware before proceeding. 3. Execute the required invalidation sequence (PASID cache, IOTLB, and Device-TLB flush) to ensure the hardware has released all cached references. 4. Only after the flushes are complete, zero out the remaining fields of the PASID entry.

Also, add a dma_wmb() in pasid_set_present() to ensure that all other fields of the PASID entry are visible to the hardware before the Present bit is set.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HLinux

Weaknesses

  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Affected Products

ProductVersions
LinuxLinux
  • 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15 to before bed36f5657d34ae982d48045a75bff6113790cf9Affected
  • 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15 to before c36b0515c6445bd137ec8ad86ef5470c45d6e4bfAffected
  • 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15 to before a84d30e8d2bacd21782a6481158b7c9c552f4868Affected
  • 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15 to before 821807c167b7b48a41b95b6607c6b9f97600f7d9Affected
  • 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15 to before 949d71666e9dd19f21e7b4b53a88cd2c5b902858Affected
  • 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15 to before 75ed00055c059dedc47b5daaaa2f8a7a019138ffAffected
LinuxLinux
  • 5.0Affected
  • before 5.0Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.75 through 6.12.*Not affected
  • 6.18.14 through 6.18.*Not affected
  • 6.19.4 through 6.19.*Not affected
  • 7.0 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.