KVM: x86/mmu: Check write tracking in all address spaces
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 699023e239658e62da6f42f47d31b54788521ec1 · < 0f38453cdb2e17566ccb7c0f3dabd5bd21caca26| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: x86/mmu: Check write tracking in all address spaces
kvm_gfn_is_write_tracked() checks only the supplied memslot, but page tracking is per-address-space and shadow pages are shared across all address spaces. With SMM, a GFN can therefore be write-tracked in one address space and appear untracked through the other.
Check the supplied slot first, then the slot for the other address space. This ensures all callers honor write tracking regardless of the active address space. In particular, it prevents mmu_try_to_unsync_pages() from marking an upper-level shadow page unsync and eventually triggering the BUG in pte_list_remove().
[invert direction of the conditional. - Paolo]
From the CVE record · Linux
KVM's x86 MMU can miss write tracking when a page is tracked in one address space but checked through another under SMM. This can lead to a kernel BUG in pte_list_remove(). The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with KVM x86 should check whether their kernel is affected; affected versions are not specified.