CVE-2024-58083
KVM: Explicitly verify target vCPU is online in kvm_get_vcpu()
Reported by linux · Published March 6, 2025
In the Linux kernel, the following vulnerability has been resolved: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() Explicitly verify the target vCPU is fully online _prior_ to clamping the index in kvm_get_vcpu(). If the index is "bad", the nospec clamping will generate '0', i.e. KVM will return vCPU0 instead of NULL. In practice, the bug is unlikely to cause problems, as it will only come into play if userspace or the guest is buggy or misbehaving, e.g. KVM may send interrupts to vCPU0 instead of dropping them on the floor. However, returning vCPU0 when it shouldn't exist per online_vcpus is problematic now that KVM uses an xarray for the vCPUs array, as KVM needs to insert into the xarray before publishing the vCPU to userspace (see commit c5b077549136 ("KVM: Convert the kvm->vcpus array to a xarray")), i.e. before vCPU creation is guaranteed to succeed. As a result, incorrectly providing access to vCPU0 will trigger a use-after-free if vCPU0 is dereferenced and kvm_vm_ioctl_create_vcpu() bails out of vCPU creation due to an error and frees vCPU0. Commit afb2acb2e3a3 ("KVM: Fix vcpu_array[0] races") papered over that issue, but in doing so introduced an unsolvable teardown conundrum. Preventing accesses to vCPU0 before it's fully online will allow reverting commit afb2acb2e3a3, without re-introducing the vcpu_array[0] UAF race.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c, 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c, 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c |
| Linux | Linux | 5.1, 0, 5.4.291 |
| linux | linux_kernel | 5.1, 5.1, 5.0.17 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2 | kernel | 0 |
| amazon:2023 | kernel-livepatch-6.1.129-138.220 | 0 |
| amazon:2 | kernel-devel | 0 |
| Siemens | SIMATIC S7-1500 TM MFP - GNU/Linux subsystem | 0 |
| amazon:2 | kernel-tools | 0 |
| amazon:2 | kernel-livepatch-4.14.355-277.647 | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | bpftool | 0 |
| Linux | Linux | 5.0.17, 6.6.78, 6.12.14 |
| amazon:2 | python-perf | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2 | kernel-tools-devel | 0 |
| amazon:2023 | python3-perf | 0 |
…and 7 more
Timeline
- Mar 6, 2025 CVE Published
- Mar 7, 2025 EPSS Score (30 in total, the first dated here)
- Mar 9, 2025 Coalition ESS Score (21 in total, the first dated here)
- Dec 29, 2025 Security Advisory (169 in total, the first dated here)
- Jan 14, 2026 PoC Published
- Mar 30, 2026 Distribution Patch (167 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-58083
vulnetix vdb fixes CVE-2024-58083
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-58083/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart