UBUNTU-CVE-2024-58083
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.
02 / AFFECTED SOFTWARE
Affected packages
11 explicit affected versions
39 explicit affected versions
45 explicit affected versions
63 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
19 explicit affected versions
6 explicit affected versions
73 explicit affected versions
24 explicit affected versions
58 explicit affected versions
76 explicit affected versions
66 explicit affected versions
59 explicit affected versions
10 explicit affected versions
17 explicit affected versions
24 explicit affected versions
65 explicit affected versions
7 explicit affected versions
64 explicit affected versions
21 explicit affected versions
104 explicit affected versions
13 explicit affected versions
77 explicit affected versions
23 explicit affected versions
35 explicit affected versions
25 explicit affected versions
23 explicit affected versions
18 explicit affected versions
24 explicit affected versions
109 explicit affected versions
64 explicit affected versions
26 explicit affected versions
106 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
31 explicit affected versions
1 explicit affected versions
21 explicit affected versions
16 explicit affected versions
10 explicit affected versions
60 explicit affected versions
27 explicit affected versions
5 explicit affected versions
7 explicit affected versions
12 explicit affected versions
4 explicit affected versions
56 explicit affected versions
12 explicit affected versions
14 explicit affected versions
1 explicit affected versions
7 explicit affected versions
2 explicit affected versions
93 explicit affected versions
12 explicit affected versions
109 explicit affected versions
117 explicit affected versions
12 explicit affected versions
21 explicit affected versions
104 explicit affected versions
19 explicit affected versions
18 explicit affected versions
13 explicit affected versions
10 explicit affected versions
37 explicit affected versions
5 explicit affected versions
13 explicit affected versions
19 explicit affected versions
10 explicit affected versions
40 explicit affected versions
1 explicit affected versions
26 explicit affected versions
13 explicit affected versions
14 explicit affected versions
1 explicit affected versions
29 explicit affected versions
96 explicit affected versions
13 explicit affected versions
70 explicit affected versions
20 explicit affected versions
21 explicit affected versions
87 explicit affected versions
65 explicit affected versions
108 explicit affected versions
28 explicit affected versions
33 explicit affected versions
23 explicit affected versions
10 explicit affected versions
1 explicit affected versions
107 explicit affected versions
11 explicit affected versions
12 explicit affected versions
130 explicit affected versions
7 explicit affected versions
12 explicit affected versions
107 explicit affected versions
56 explicit affected versions
50 explicit affected versions
122 explicit affected versions
66 explicit affected versions
144 explicit affected versions
10 explicit affected versions
26 explicit affected versions
25 explicit affected versions
41 explicit affected versions
1 explicit affected versions
14 explicit affected versions
26 explicit affected versions
13 explicit affected versions
26 explicit affected versions
130 explicit affected versions
64 explicit affected versions
16 explicit affected versions
67 explicit affected versions
29 explicit affected versions
54 explicit affected versions
3 explicit affected versions
84 explicit affected versions
1 explicit affected versions
4 explicit affected versions
2 explicit affected versions
74 explicit affected versions
51 explicit affected versions
83 explicit affected versions
13 explicit affected versions
23 explicit affected versions
12 explicit affected versions
53 explicit affected versions
27 explicit affected versions
40 explicit affected versions
1 explicit affected versions
88 explicit affected versions
22 explicit affected versions
8 explicit affected versions
30 explicit affected versions
5 explicit affected versions
8 explicit affected versions
1 explicit affected versions
10 explicit affected versions
4 explicit affected versions
25 explicit affected versions
13 explicit affected versions
96 explicit affected versions
13 explicit affected versions
59 explicit affected versions
7 explicit affected versions
3 explicit affected versions
85 explicit affected versions
57 explicit affected versions
10 explicit affected versions
12 explicit affected versions
15 explicit affected versions
94 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
45 explicit affected versions
37 explicit affected versions
30 explicit affected versions
14 explicit affected versions
38 explicit affected versions
9 explicit affected versions
55 explicit affected versions
11 explicit affected versions
19 explicit affected versions
7 explicit affected versions
66 explicit affected versions
7 explicit affected versions
35 explicit affected versions
67 explicit affected versions
134 explicit affected versions
113 explicit affected versions
4 explicit affected versions
1 explicit affected versions
1 explicit affected versions
1 explicit affected versions
64 explicit affected versions
104 explicit affected versions
56 explicit affected versions
13 explicit affected versions
43 explicit affected versions
62 explicit affected versions
158 explicit affected versions
10 explicit affected versions
8 explicit affected versions
24 explicit affected versions
14 explicit affected versions
92 explicit affected versions
4 explicit affected versions
78 explicit affected versions
11 explicit affected versions
1 explicit affected versions
60 explicit affected versions
19 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
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.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/1e7381f3617d14b3c11da80ff5f8a93ab14cfc46
- https://git.kernel.org/stable/c/125da53b3c0c9d7f58353aea0076e9efd6498ba7
- https://git.kernel.org/stable/c/1e7381f3617d14b3c11da80ff5f8a93ab14cfc46
- https://git.kernel.org/stable/c/ca8da90ed1432ff3d000de4f1e2275d4e7d21b96
- https://git.kernel.org/stable/c/d817e510662fd1c9797952408d94806f97a5fffd
- https://git.kernel.org/stable/c/f2f805ada63b536bc192458a7098388286568ad4
- https://ubuntu.com/security/CVE-2024-58083
- https://ubuntu.com/security/notices/USN-7510-1
- https://ubuntu.com/security/notices/USN-7510-2
- https://ubuntu.com/security/notices/USN-7510-3
- https://ubuntu.com/security/notices/USN-7510-4
- https://ubuntu.com/security/notices/USN-7510-5
- https://ubuntu.com/security/notices/USN-7510-6
- https://ubuntu.com/security/notices/USN-7510-7
- https://ubuntu.com/security/notices/USN-7510-8
- https://ubuntu.com/security/notices/USN-7511-1
- https://ubuntu.com/security/notices/USN-7511-2
- https://ubuntu.com/security/notices/USN-7511-3
- https://ubuntu.com/security/notices/USN-7512-1
- https://ubuntu.com/security/notices/USN-7516-1
- https://ubuntu.com/security/notices/USN-7516-2
- https://ubuntu.com/security/notices/USN-7516-3
- https://ubuntu.com/security/notices/USN-7516-4
- https://ubuntu.com/security/notices/USN-7516-5
- https://ubuntu.com/security/notices/USN-7516-6
- https://ubuntu.com/security/notices/USN-7516-7
- https://ubuntu.com/security/notices/USN-7516-8
- https://ubuntu.com/security/notices/USN-7516-9
- https://ubuntu.com/security/notices/USN-7517-1
- https://ubuntu.com/security/notices/USN-7517-2
- https://ubuntu.com/security/notices/USN-7517-3
- https://ubuntu.com/security/notices/USN-7518-1
- https://ubuntu.com/security/notices/USN-7521-1
- https://ubuntu.com/security/notices/USN-7521-2
- https://ubuntu.com/security/notices/USN-7521-3
- https://ubuntu.com/security/notices/USN-7539-1
- https://ubuntu.com/security/notices/USN-7540-1
- https://ubuntu.com/security/notices/USN-7593-1
- https://ubuntu.com/security/notices/USN-7602-1
- https://ubuntu.com/security/notices/USN-7640-1
- https://ubuntu.com/security/notices/USN-7651-1
- https://ubuntu.com/security/notices/USN-7651-2
- https://ubuntu.com/security/notices/USN-7651-3
- https://ubuntu.com/security/notices/USN-7651-4
- https://ubuntu.com/security/notices/USN-7651-5
- https://ubuntu.com/security/notices/USN-7651-6
- https://ubuntu.com/security/notices/USN-7652-1
- https://ubuntu.com/security/notices/USN-7653-1
- https://ubuntu.com/security/notices/USN-7737-1
- https://ubuntu.com/security/notices/USN-7907-1
- https://ubuntu.com/security/notices/USN-7907-2
- https://ubuntu.com/security/notices/USN-7907-3
- https://ubuntu.com/security/notices/USN-7907-4
- https://ubuntu.com/security/notices/USN-7907-5
- https://ubuntu.com/security/notices/USN-7937-1
- https://www.cve.org/CVERecord?id=CVE-2024-58083