KVM: TDX: Reject concurrent change to CPUID entry count
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: TDX: Reject concurrent change to CPUID entry count
Reject KVM_TDX_INIT_VM if userspace changes cpuid.nent between the initial read and the subsequent copy of the initialization data.
tdx_td_init() first reads user_data->cpuid.nent to size the flexible kvm_tdx_init_vm copy. The copied structure also contains cpuid.nent, and that field can differ from the value used to size the allocation if userspace modifies the input concurrently. setup_tdparams_cpuids() later passes init_vm->cpuid.nent to kvm_find_cpuid_entry2(), which uses it as the array bound for the copied entries.
Require the copied count to match the value used to size the allocation so that CPUID parsing cannot access beyond the entries actually copied.
From the CVE record · Linux
The Linux kernel’s KVM TDX initialization path can use a CPUID entry count larger than the array it copied. Local userspace can trigger an out-of-bounds access during KVM_TDX_INIT_VM by changing that count between the initial read and the copy; the input does not specify an authentication requirement.
Engineers running Linux kernels with KVM TDX should check their builds; affected versions are not specified.