CVE 7.8 HIGH

iommu/vt-d: Clear Present bit before tearing down PASID entry_CVE-2026-45894

7.8 / 10
HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

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.

Basic Information

ID CVE-2026-45894
Source Linux
Published May 27, 2026 at 12:17
Modified May 30, 2026 at 10:45

Affected Product

Vendor Linux
Product Linux
Version 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15
Affected Versions Linux Linux 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15
Linux Linux 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15
Linux Linux 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15
Linux Linux 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15
Linux Linux 5.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.