iommu/vt-d: Remove WO permissions on second-level paging entries
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/vt-d: Remove WO permissions on second-level paging entries
When the first level page table is used for IOVA translation, it only supports Read-Only and Read-Write permissions. The Write-Only permission is not supported as the PRESENT bit (implying Read permission) should always set. When using second level, we still give separate permissions that allows WriteOnly which seems inconsistent and awkward. We want to have consistent behavior. After moving to 1st level, we don't want things to work sometimes, and break if we use 2nd level for the same mappings. Hence remove this configuration.
From the CVE record · Linux
The Linux kernel’s IOMMU VT-d second-level paging entries allowed write-only permissions, while first-level paging does not support them. The input does not describe an attacker action or specify network access, authentication, or user-interaction requirements.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.