kvm: s390: Reject memory region operations for ucontrol VMs
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: s390: Reject memory region operations for ucontrol VMs
This change rejects the KVM_SET_USER_MEMORY_REGION and KVM_SET_USER_MEMORY_REGION2 ioctls when called on a ucontrol VM. This is necessary since ucontrol VMs have kvm->arch.gmap set to 0 and would thus result in a null pointer dereference further in. Memory management needs to be performed in userspace and using the ioctls KVM_S390_UCAS_MAP and KVM_S390_UCAS_UNMAP.
Also improve s390 specific documentation for KVM_SET_USER_MEMORY_REGION and KVM_SET_USER_MEMORY_REGION2.
[frankja@linux.ibm.com: commit message spelling fix, subject prefix fix]
From the CVE record · Linux
The Linux kernel’s s390 KVM implementation can dereference a null pointer when KVM_SET_USER_MEMORY_REGION or KVM_SET_USER_MEMORY_REGION2 is called on a ucontrol VM. An attacker able to issue these ioctls on a ucontrol VM could trigger the dereference; the input does not specify authentication requirements or user interaction.
Engineers running Linux kernels with s390 KVM ucontrol VMs should check their deployments; affected versions are not specified.