KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 78824fabc72e5e37d51e6e567fde70a4fc41a6d7 · < 28cc13ca20431b127d42d84ba10898d03e2c8267| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION
Drop the WARN in sev_pin_memory() on npages overflowing an int, as the WARN is comically trivially to trigger from userspace, e.g. by doing:
struct kvm_enc_region range = { .addr = 0, .size = -1ul, };
__vm_ioctl(vm, KVM_MEMORY_ENCRYPT_REG_REGION, &range);
Note, the checks in sev_mem_enc_register_region() that presumably exist to verify the incoming address+size are completely worthless, as both "addr" and "size" are u64s and SEV is 64-bit only, i.e. they _can't_ be greater than ULONG_MAX. That wart will be cleaned up in the near future.
if (range->addr > ULONG_MAX || range->size > ULONG_MAX) return -EINVAL;
Opportunistically add a comment to explain why the code calculates the number of pages the "hard" way, e.g. instead of just shifting @ulen.
From the CVE record · Linux
The Linux kernel’s KVM SEV memory-registration path can issue a warning when a requested region size overflows an integer page count. A local userspace process that can issue the KVM_MEMORY_ENCRYPT_REG_REGION ioctl on a VM can trigger the warning with an oversized region; no user interaction is described.
Engineers running Linux kernels with KVM SEV should check whether their kernel includes the fix; affected versions are not specified.