KVM: x86/mmu: Write-protect L2 SPTEs in TDP MMU when clearing dirty status
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 |
|
|
6.6.296.8.86.9In the Linux kernel, the following vulnerability has been resolved:
KVM: x86/mmu: Write-protect L2 SPTEs in TDP MMU when clearing dirty status
Check kvm_mmu_page_ad_need_write_protect() when deciding whether to write-protect or clear D-bits on TDP MMU SPTEs, so that the TDP MMU accounts for any role-specific reasons for disabling D-bit dirty logging.
Specifically, TDP MMU SPTEs must be write-protected when the TDP MMU is being used to run an L2 (i.e. L1 has disabled EPT) and PML is enabled. KVM always disables PML when running L2, even when L1 and L2 GPAs are in the some domain, so failing to write-protect TDP MMU SPTEs will cause writes made by L2 to not be reflected in the dirty log.
[sean: massage shortlog and changelog, tweak ternary op formatting]
From the CVE record · Linux
The Linux kernel’s KVM TDP MMU can fail to write-protect L2 page-table entries when clearing dirty status. When L1 has disabled EPT and PML is enabled, writes made by an L2 guest may not appear in the dirty log. The input does not specify network access or authentication requirements.
Operators running Linux kernels with KVM x86 TDP MMU should check their versions; affected versions are not specified in the input.