KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation
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:
KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation
walk_s1() and kvm_walk_nested_s2() expect to be called while holding kvm->srcu to guard against memslot changes. While this is generally the case, __kvm_at_s12() and __kvm_find_s1_desc_level() call into the respective walkers without taking kvm->srcu.
Fix by acquiring kvm->srcu prior to the table walk in both instances.
From the CVE record · Linux
Linux KVM on arm64 performs some page-table walks during fault injection and AT emulation without holding the SRCU lock that guards against memslot changes. This can allow a walk to race with a memslot change; the input does not specify an attacker action or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with KVM on arm64 should check their versions against the vendor advisory; affected versions are not specified.