KVM: arm64: Validate the SVE vector length in pkvm_vcpu_init_sve()
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.557.2.97.3In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Validate the SVE vector length in pkvm_vcpu_init_sve()
pkvm_vcpu_init_sve() clamps only the upper bound of the host-provided sve_max_vl, so an invalid vector length reaches sve_state_size_from_vl() and the WARN_ON() there, which is fatal at EL2. The existing !sve_state_size test rejects such a length, but only after the macro has run.
Check sve_vl_valid() before deriving the state size. A valid length cannot yield a zero size, so the !sve_state_size test goes with it.
From the CVE record · Linux
KVM arm64 does not validate the lower bound of a host-provided SVE vector length before calculating the vCPU state size. An invalid length can trigger a warning that is fatal at EL2; the input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with KVM arm64 should check whether their kernel includes the fix; affected versions are not specified.