CVE-2024-58083

Advisory lineage Upstream: 0 Downstream: 66
Modified
Published: 06 Mar 2025, 16:13
Last modified:23 May 2026, 15:56

Vulnerability Summary

Overall Risk (default)
medium
31/100
CVSS Score
7.8 HIGH
v3.1 (cve.org)
EPSS Score
0.03% LOW
0% probability -0.01%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

06 Mar 2025, 16:13
Published
Vulnerability first disclosed
23 May 2026, 15:56
Last Modified
Vulnerability information updated

Description

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.

CVSS Metrics

  • v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.03%• Percentile: 8%

Techniques & Countermeasures

  • CWE-416•Use After Free

    The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

  • linux•linux

    ≥ 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c, < 5cce2ed69b00e022b5cdf0c49c82986abd2941a8 | ≥ 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c, < 09d50ccf0b2d739db4a485b08afe7520a4402a63 | ≥ 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c, < 7c4899239d0f70f88ac42665b3da51678d122480 | ≥ 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c, < d817e510662fd1c9797952408d94806f97a5fffd | ≥ 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c, < 125da53b3c0c9d7f58353aea0076e9efd6498ba7 | ≥ 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c, < f2f805ada63b536bc192458a7098388286568ad4 | ≥ 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c, < ca8da90ed1432ff3d000de4f1e2275d4e7d21b96 | ≥ 1d487e9bf8ba66a7174c56a0029c54b1eca8f99c, < 1e7381f3617d14b3c11da80ff5f8a93ab14cfc46 | 559e2696d2f47a3575e9550f101a7e59e30b1b38 | d39f3cc71382165bb7efb8e06a2bd32f847de4ae | 7cee966029037a183d98cb88251ceb92a233fe63 | ≥ 4.14.120, < 4.15 | ≥ 4.19.44, < 4.20 | ≥ 5.0.17, < 5.1 | 5.1

  • linux•linux_kernel

    ≥ 4.14.120, < 4.15 | ≥ 4.19.44, < 4.20 | ≥ 5.0.17, < 5.4.291 | ≥ 5.5, < 5.10.235 | ≥ 5.11, < 5.15.179 | ≥ 5.16, < 6.1.129 | ≥ 6.2, < 6.6.78 | ≥ 6.7, < 6.12.14 | ≥ 6.13, < 6.13.3

References (10)