iommu/vt-d: Flush cache for PASID table before using it
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 194b3348bdbb7db65375c72f3f774aee4cc6614e · < 36244dfd3853f7bf89d03b8e90d56b23ce7fbc16| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
iommu/vt-d: Flush cache for PASID table before using it
When writing the address of a freshly allocated zero-initialized PASID table to a PASID directory entry, do that after the CPU cache flush for this PASID table, not before it, to avoid the time window when this PASID table may be already used by non-coherent IOMMU hardware while its contents in RAM is still some random old data, not zero-initialized.
From the CVE record · Linux
The Linux kernel can publish a new PASID table before flushing its CPU cache. During that window, non-coherent IOMMU hardware may read stale data from RAM instead of the zero-initialized table. The input does not establish how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running the Linux kernel with iommu/vt-d should check their deployments; affected versions are not specified.