CVE-2024-58083

一、漏洞信息
漏洞编号：CVE-2024-58083
漏洞归属组件：kernel
漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.4.0,6.6.0
CVSS V3.0分值：
BaseScore：7.8 High
Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
漏洞简述：
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 theindex in kvm_get_vcpu(). If the index is bad , the nospec clamping willgenerate 0 , i.e. KVM will return vCPU0 instead of NULL.In practice, the bug is unlikely to cause problems, as it will only comeinto play if userspace or the guest is buggy or misbehaving, e.g. KVM maysend interrupts to vCPU0 instead of dropping them on the floor.However, returning vCPU0 when it shouldn t exist per online_vcpus isproblematic now that KVM uses an xarray for the vCPUs array, as KVM needsto insert into the xarray before publishing the vCPU to userspace (seecommit 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 ause-after-free if vCPU0 is dereferenced and kvm_vm_ioctl_create_vcpu()bails out of vCPU creation due to an error and frees vCPU0. Commitafb2acb2e3a3 ( KVM: Fix vcpu_array[0] races ) papered over that issue, butin doing so introduced an unsolvable teardown conundrum. Preventingaccesses to vCPU0 before it s fully online will allow reverting commitafb2acb2e3a3, without re-introducing the vcpu_array[0] UAF race.
漏洞公开时间：2025-03-07 01:15:21
漏洞创建时间：2025-03-07 01:37:10
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2024-58083

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/09d50ccf0b2d739db4a485b08afe7520a4402a63
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/125da53b3c0c9d7f58353aea0076e9efd6498ba7
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/1e7381f3617d14b3c11da80ff5f8a93ab14cfc46
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/5cce2ed69b00e022b5cdf0c49c82986abd2941a8
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/7c4899239d0f70f88ac42665b3da51678d122480
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/ca8da90ed1432ff3d000de4f1e2275d4e7d21b96
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/d817e510662fd1c9797952408d94806f97a5fffd
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/f2f805ada63b536bc192458a7098388286568ad4
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-58083	https://bugzilla.suse.com/show_bug.cgi?id=1239036
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2024-58083	https://bugzilla.suse.com/show_bug.cgi?id=1239036
suse_bugzilla	https://git.kernel.org/stable/c/125da53b3c0c9d7f58353aea0076e9efd6498ba7	https://bugzilla.suse.com/show_bug.cgi?id=1239036
suse_bugzilla	https://git.kernel.org/stable/c/1e7381f3617d14b3c11da80ff5f8a93ab14cfc46	https://bugzilla.suse.com/show_bug.cgi?id=1239036
suse_bugzilla	https://git.kernel.org/stable/c/ca8da90ed1432ff3d000de4f1e2275d4e7d21b96	https://bugzilla.suse.com/show_bug.cgi?id=1239036
suse_bugzilla	https://git.kernel.org/stable/c/d817e510662fd1c9797952408d94806f97a5fffd	https://bugzilla.suse.com/show_bug.cgi?id=1239036
suse_bugzilla	https://git.kernel.org/stable/c/f2f805ada63b536bc192458a7098388286568ad4	https://bugzilla.suse.com/show_bug.cgi?id=1239036
suse_bugzilla	https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-58083.mbox	https://bugzilla.suse.com/show_bug.cgi?id=1239036
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2025030610-CVE-2024-58083-62b7@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2350388
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2025030610-CVE-2024-58083-62b7@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2350388
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2025030610-CVE-2024-58083-62b7@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2350388
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2025030610-CVE-2024-58083-62b7@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2350388
debian		https://security-tracker.debian.org/tracker/CVE-2024-58083
anolis		https://anas.openanolis.cn/cves/detail/CVE-2024-58083

漏洞分析指导链接：
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息：

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
		https://git.kernel.org/stable/c/09d50ccf0b2d739db4a485b08afe7520a4402a63		nvd
		https://git.kernel.org/stable/c/125da53b3c0c9d7f58353aea0076e9efd6498ba7		nvd
		https://git.kernel.org/stable/c/1e7381f3617d14b3c11da80ff5f8a93ab14cfc46		nvd
		https://git.kernel.org/stable/c/5cce2ed69b00e022b5cdf0c49c82986abd2941a8		nvd
		https://git.kernel.org/stable/c/7c4899239d0f70f88ac42665b3da51678d122480		nvd
		https://git.kernel.org/stable/c/ca8da90ed1432ff3d000de4f1e2275d4e7d21b96		nvd
		https://git.kernel.org/stable/c/d817e510662fd1c9797952408d94806f97a5fffd		nvd
		https://git.kernel.org/stable/c/f2f805ada63b536bc192458a7098388286568ad4		nvd
linux_kernel	6.1.129	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d817e510662fd1c9797952408d94806f97a5fffdIssue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c	linuxkernelcves
linux_kernel	6.6.78	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=125da53b3c0c9d7f58353aea0076e9efd6498ba7Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c	linuxkernelcves
linux_kernel	6.12.14	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f2f805ada63b536bc192458a7098388286568ad4Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c	linuxkernelcves
linux_kernel	6.13.3	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ca8da90ed1432ff3d000de4f1e2275d4e7d21b96Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c	linuxkernelcves
linux_kernel	6.14-rc1	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1e7381f3617d14b3c11da80ff5f8a93ab14cfc46Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1d487e9bf8ba66a7174c56a0029c54b1eca8f99c	linuxkernelcves

二、漏洞分析结构反馈
影响性分析说明：
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 theindex in kvm_get_vcpu(). If the index is bad , the nospec clamping willgenerate 0 , i.e. KVM will return vCPU0 instead of NULL.In practice, the bug is unlikely to cause problems, as it will only comeinto play if userspace or the guest is buggy or misbehaving, e.g. KVM maysend interrupts to vCPU0 instead of dropping them on the floor.However, returning vCPU0 when it shouldn t exist per online_vcpus isproblematic now that KVM uses an xarray for the vCPUs array, as KVM needsto insert into the xarray before publishing the vCPU to userspace (seecommit 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 ause-after-free if vCPU0 is dereferenced and kvm_vm_ioctl_create_vcpu()bails out of vCPU creation due to an error and frees vCPU0. Commitafb2acb2e3a3 ( KVM: Fix vcpu_array[0] races ) papered over that issue, butin doing so introduced an unsolvable teardown conundrum. Preventingaccesses to vCPU0 before it s fully online will allow reverting commitafb2acb2e3a3, without re-introducing the vcpu_array[0] UAF race.
openEuler评分：
7.8
Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
受影响版本排查(受影响/不受影响)：
1.openEuler-20.03-LTS-SP4(4.19.90):受影响
2.openEuler-22.03-LTS-SP3(5.10.0):受影响
3.openEuler-22.03-LTS-SP4(5.10.0):受影响
4.openEuler-24.03-LTS(6.6.0):受影响
5.openEuler-24.03-LTS-SP1(6.6.0):受影响
6.master(6.12.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP4(4.19.90):否
2.openEuler-22.03-LTS-SP3(5.10.0):否
3.master(6.12.0):否
4.openEuler-24.03-LTS(6.6.0):否
5.openEuler-24.03-LTS-Next(6.6.0):否
6.openEuler-22.03-LTS-SP4(5.10.0):否
7.openEuler-24.03-LTS-SP1(6.6.0):否

原因说明：
1.openEuler-24.03-LTS(6.6.0):正常修复
2.openEuler-24.03-LTS-SP1(6.6.0):正常修复
3.openEuler-20.03-LTS-SP4(4.19.90):不修复-超出修复范围
4.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围
5.openEuler-22.03-LTS-SP4(5.10.0):不修复-超出修复范围
6.master(6.12.0):不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-1649

Hi openeuler-ci-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Kernel, and any of the maintainers.

@yangyingliang ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 ,@gasonchen 
**issue处理注意事项:** 
**1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;**
**2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;**
**3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.**
************************************************************************
影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响): 
1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP3(5.10.0):
4.openEuler-22.03-LTS-SP4(5.10.0):
5.openEuler-24.03-LTS(6.6.0):
6.openEuler-24.03-LTS-Next(6.6.0):
7.openEuler-24.03-LTS-SP1(6.6.0):

修复是否涉及abi变化(是/否)：
1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP3(5.10.0):
4.openEuler-22.03-LTS-SP4(5.10.0):
5.openEuler-24.03-LTS(6.6.0):
6.openEuler-24.03-LTS-Next(6.6.0):
7.openEuler-24.03-LTS-SP1(6.6.0):

原因说明：
1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP3(5.10.0):
4.openEuler-22.03-LTS-SP4(5.10.0):
5.openEuler-24.03-LTS(6.6.0):
6.openEuler-24.03-LTS-Next(6.6.0):
7.openEuler-24.03-LTS-SP1(6.6.0):

issue处理具体操作请参考: 
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

参考网址	关联pr	状态	补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2024-58083	None	None	https://git.kernel.org/stable/c/f2f805ada63b536bc192458a7098388286568ad4 https://git.kernel.org/stable/c/ca8da90ed1432ff3d000de4f1e2275d4e7d21b96 https://git.kernel.org/stable/c/d817e510662fd1c9797952408d94806f97a5fffd https://git.kernel.org/stable/c/1e7381f3617d14b3c11da80ff5f8a93ab14cfc46 https://git.kernel.org/stable/c/125da53b3c0c9d7f58353aea0076e9efd6498ba7
https://ubuntu.com/security/CVE-2024-58083	None	None	https://discourse.ubuntu.com/c/project
https://www.opencve.io/cve/CVE-2024-58083	None	None	https://git.kernel.org/stable/c/f2f805ada63b536bc192458a7098388286568ad4 https://git.kernel.org/stable/c/ca8da90ed1432ff3d000de4f1e2275d4e7d21b96 https://git.kernel.org/stable/c/d817e510662fd1c9797952408d94806f97a5fffd https://git.kernel.org/stable/c/1e7381f3617d14b3c11da80ff5f8a93ab14cfc46 https://git.kernel.org/stable/c/125da53b3c0c9d7f58353aea0076e9efd6498ba7
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-58083
https://security-tracker.debian.org/tracker/CVE-2024-58083
http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2024-58083

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

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.

The Linux kernel CVE team has assigned CVE-2024-58083 to this issue.

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.master(6.1.0):不受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:受影响

修复是否涉及abi变化(是/否)：
1.master(6.1.0):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS-SP3:否
4.openEuler-22.03-LTS-SP4:否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-24.03-LTS-SP1:否

原因说明：
1.master(23.08.5):不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:不修复-超出修复范围
4.openEuler-22.03-LTS-SP3:正常修复
5.openEuler-22.03-LTS-SP4:正常修复
6.openEuler-24.03-LTS:正常修复
7.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
8.openEuler-24.03-LTS-SP1:正常修复

@CTC-XiboWang 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 分析项目 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|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 theindex in kvm_get_vcpu().  If the index is &#34;bad&#34;, the nospec clamping willgenerate &#39;0&#39;, i.e. KVM will return vCPU0 instead of NULL.In practice, the bug is unlikely to cause problems, as it will only comeinto play if userspace or the guest is buggy or misbehaving, e.g. KVM maysend interrupts to vCPU0 instead of dropping them on the floor.However, returning vCPU0 when it shouldn&#39;t exist per online_vcpus isproblematic now that KVM uses an xarray for the vCPUs array, as KVM needsto insert into the xarray before publishing the vCPU to userspace (seecommit c5b077549136 (&#34;KVM: Convert the kvm-&gt;vcpus array to a xarray&#34;)),i.e. before vCPU creation is guaranteed to succeed.As a result, incorrectly providing access to vCPU0 will trigger ause-after-free if vCPU0 is dereferenced and kvm_vm_ioctl_create_vcpu()bails out of vCPU creation due to an error and frees vCPU0.  Commitafb2acb2e3a3 (&#34;KVM: Fix vcpu_array[0] races&#34;) papered over that issue, butin doing so introduced an unsolvable teardown conundrum.  Preventingaccesses to vCPU0 before it&#39;s fully online will allow reverting commitafb2acb2e3a3, without re-introducing the vcpu_array[0] UAF race.The Linux kernel CVE team has assigned CVE-2024-58083 to this issue.|
|已分析|2.openEulerScore|5.5|
|已分析|3.openEulerVector|AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-SP1:受影响,master:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.是否涉及abi变化|master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否|
|已分析|6.原因说明|openEuler-22.03-LTS-SP3:正常修复,openEuler-22.03-LTS-SP4:正常修复,openEuler-24.03-LTS:正常修复,openEuler-24.03-LTS-SP1:正常修复,openEuler-20.03-LTS-SP4:不修复-超出修复范围,master:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发|

**请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.**