Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2026-45894

high

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 Mod…

Vendor / product: Linux — linux kernel

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.

CVSS
7.8
7.8 (CVSS v3.1)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Severity source: NVD CVSS v3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
Timeline (UTC)
Published: 2026-05-27 14:17
Modified: 2026-10-30 13:18
NVD status: Modified
Last synced 1 day ago
Verified against the source API 2026-10-30 13:38 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥5.0 <6.12.75, ≥6.13 <6.18.14, ≥6.19 <6.19.4

Weakness classification (CWE)

NVD-CWE-noinfo CWE-362

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/75ed00055c059dedc47b5daaaa2f8a7a019138ff
Patch / mitigation: https://git.kernel.org/stable/c/821807c167b7b48a41b95b6607c6b9f97600f7d9
Patch / mitigation: https://git.kernel.org/stable/c/949d71666e9dd19f21e7b4b53a88cd2c5b902858
Patch / mitigation: https://git.kernel.org/stable/c/a84d30e8d2bacd21782a6481158b7c9c552f4868

References

Data sources

NVD CVE API 2.0 — fetched 2026-10-30 13:38 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs