CVE-2024-58083
Last modified
CVE-2024-58083 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.14.120, < 4.15 |
| Linux | Linux Kernel | >= 4.19.44, < 4.20 |
| Linux | Linux Kernel | >= 5.0.17, < 5.4.291 |
| Linux | Linux Kernel | >= 5.5, < 5.10.235 |
| Linux | Linux Kernel | >= 5.11, < 5.15.179 |
| Linux | Linux Kernel | >= 5.16, < 6.1.129 |
| Linux | Linux Kernel | >= 6.2, < 6.6.78 |
| Linux | Linux Kernel | >= 6.7, < 6.12.14 |
| Linux | Linux Kernel | >= 6.13, < 6.13.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-58083?
How severe is CVE-2024-58083?
How do I fix CVE-2024-58083?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-58078In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-58079In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5808The WP Ajax Contact Form WordPress plugin through 2.2.2 does…4.3
- CVE-2024-58080In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-58081In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-58082In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-58084In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-58085In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-58086In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-58087In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2024-58088In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-58089In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-58083?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
