LoongArch: KVM: Handle the case that EIOINTC's coremap is empty
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.216.19.117.0In the Linux kernel, the following vulnerability has been resolved:
LoongArch: KVM: Handle the case that EIOINTC's coremap is empty
EIOINTC's coremap in eiointc_update_sw_coremap() can be empty, currently we get a cpuid with -1 in this case, but we actually need 0 because it's similar as the case that cpuid >= 4.
This fix an out-of-bounds access to kvm_arch::phyid_map::phys_map[].
From the CVE record · Linux
An empty EIOINTC coremap can cause an out-of-bounds access in the Linux kernel’s LoongArch KVM code. The input does not specify an attacker action or whether exploitation requires network access, authentication, local access, or user interaction.
Engineers running Linux kernels with LoongArch KVM should check their installations; affected versions are not specified.