iommu/sva: invalidate stale IOTLB entries for kernel address space
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
iommu/sva: invalidate stale IOTLB entries for kernel address space
Introduce a new IOMMU interface to flush IOTLB paging cache entries for the CPU kernel address space. This interface is invoked from the x86 architecture code that manages combined user and kernel page tables, specifically before any kernel page table page is freed and reused.
This addresses the main issue with vfree() which is a common occurrence and can be triggered by unprivileged users. While this resolves the primary problem, it doesn't address some extremely rare case related to memory unplug of memory that was present as reserved memory at boot, which cannot be triggered by unprivileged users. The discussion can be found at the link below.
Enable SVA on x86 architecture since the IOMMU can now receive notification to flush the paging cache before freeing the CPU kernel page table pages.
From the CVE record · Linux
The Linux kernel can retain stale IOTLB paging-cache entries when kernel page-table pages are freed and reused. Unprivileged users can trigger the primary issue through vfree(); the input does not describe a network attack or required user interaction. A separate, extremely rare memory-unplug case cannot be triggered by unprivileged users.
Engineers running Linux kernels with IOMMU SVA should check their vendor's affected-version guidance; no versions are specified in the input.