KVM: arm64: Correctly cap TLBI Range to the architural limit
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.18.517.2.57.3In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Correctly cap TLBI Range to the architural limit
TLB Invalidation by Range has a fairly powerful way of encoding pretty large ranges in a small number of bits. This range can be based on an arbitrary VA, which means it is pretty easy for a guest to generate an overflow should the hypervisor be naive enough to add the range to the base...
Make sure the range is capped to the limit dictated by the address bit that determines the VA range. For an IPA invalidation, this is further corrected down the line to ignore the upper range.
From the CVE record · Linux
Linux kernel KVM on arm64 does not correctly cap TLBI Range invalidations to the architectural limit. A guest can use an arbitrary virtual address to generate a range overflow in the hypervisor. This requires control of a guest; the input does not specify any further authentication or user-interaction requirements.
Operators running Linux kernels with KVM on arm64 should check their versions against the vendor advisory; affected versions are not specified.