KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6211753fdfd05af9e08f54c8d0ba3ee516034878 · < 3e6245ebe7ef341639e9a7e402b3ade8ad45a19f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3
On a system with a GICv3, if a guest hasn't been configured with GICv3 and that the host is not capable of GICv2 emulation, a write to any of the ICC_*SGI*_EL1 registers is trapped to EL2.
We therefore try to emulate the SGI access, only to hit a NULL pointer as no private interrupt is allocated (no GIC, remember?).
The obvious fix is to give the guest what it deserves, in the shape of a UNDEF exception.
From the CVE record · Linux
On a GICv3 system, KVM arm64 can dereference a NULL pointer if a guest without GICv3 writes to an ICC_*SGI*_EL1 register and the host cannot emulate GICv2. The guest write is trapped to the host, which attempts to emulate it without an allocated private interrupt. The input does not establish a network attack path or any required user interaction.
Operators running Linux kernel KVM on arm64 systems with GICv3 should check their kernels; affected versions are not specified.