登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
模力方舟
登录
注册
代码拉取完成，页面将自动刷新
开源项目
>
其他开源
>
操作系统
&&
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
113
Star
72
Fork
314
src-openEuler
/
kernel
代码
Issues
937
Pull Requests
42
Wiki
统计
流水线
服务
JavaDoc
PHPDoc
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
SBOM
我知道了，不再自动展开
更新失败，请稍后重试！
移除标识
内容风险标识
本任务被
标识为内容中包含有代码安全 Bug 、隐私泄露等敏感信息，仓库外成员不可访问
CVE-2025-38211
已完成
#ICK4S4
CVE和安全问题
openeuler-ci-bot
拥有者
创建于
2025-07-04 23:01
一、漏洞信息 漏洞编号：[CVE-2025-38211](https://nvd.nist.gov/vuln/detail/CVE-2025-38211) 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/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：N/A None Vector：CVSS：3.0/ 漏洞简述： A use-after-free vulnerability exists in the RDMA/iwcm component of the Linux kernel. The vulnerability occurs when work objects of cm_id_private are still in use by event handlers after cm_id destruction. While previous patches attempted to address this by flushing pending works, decrementing the last reference to cm_id within the event handler work leads to removal of the work object itself, triggering the use-after-free BUG. 漏洞公开时间：2025-07-04 22:15:29 漏洞创建时间：2025-07-04 23:01:54 漏洞详情参考链接： https://nvd.nist.gov/vuln/detail/CVE-2025-38211 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | | https://git.kernel.org/stable/c/23a707bbcbea468eedb398832eeb7e8e0ceafd21 | | | | https://git.kernel.org/stable/c/3b4a50d733acad6831f6bd9288a76a80f70650ac | | | | https://git.kernel.org/stable/c/6883b680e703c6b2efddb4e7a8d891ce1803d06b | | | | https://git.kernel.org/stable/c/764c9f69beabef8bdc651a7746c59f7a340d104f | | | | https://git.kernel.org/stable/c/78381dc8a6b61c9bb9987d37b4d671b99767c4a1 | | | | https://git.kernel.org/stable/c/fd960b5ddf4faf00da43babdd3acda68842e1f6a | | | | https://security-tracker.debian.org/tracker/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | </details> 漏洞分析指导链接： https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: 七彩瞬析开源风险感知平台 漏洞补丁信息： <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | gregkh/linux | | https://github.com/gregkh/linux/commit/23a707bbcbea468eedb398832eeb7e8e0ceafd21.patch | | ljqc | | | | https://git.kernel.org/stable/c/23a707bbcbea468eedb398832eeb7e8e0ceafd21 | | nvd | | | | https://git.kernel.org/stable/c/3b4a50d733acad6831f6bd9288a76a80f70650ac | | nvd | | | | https://git.kernel.org/stable/c/6883b680e703c6b2efddb4e7a8d891ce1803d06b | | nvd | | | | https://git.kernel.org/stable/c/764c9f69beabef8bdc651a7746c59f7a340d104f | | nvd | | | | https://git.kernel.org/stable/c/78381dc8a6b61c9bb9987d37b4d671b99767c4a1 | | nvd | | | | https://git.kernel.org/stable/c/fd960b5ddf4faf00da43babdd3acda68842e1f6a | | nvd | | | | https://git.kernel.org/stable/c/013dcdf6f03bcedbaf1669e3db71c34a197715b2 | | nvd | | | | https://git.kernel.org/stable/c/bf7eff5e3a36c54bbe8aff7fd6dd7c07490b81c5 | | nvd | | | | https://git.kernel.org/stable/c/013dcdf6f03bcedbaf1669e3db71c34a197715b2 | | cvelistv5 | | | | https://git.kernel.org/stable/c/bf7eff5e3a36c54bbe8aff7fd6dd7c07490b81c5 | | cvelistv5 | | | | https://git.kernel.org/stable/c/3b4a50d733acad6831f6bd9288a76a80f70650ac | | cvelistv5 | | | | https://git.kernel.org/stable/c/78381dc8a6b61c9bb9987d37b4d671b99767c4a1 | | cvelistv5 | | | | https://git.kernel.org/stable/c/23a707bbcbea468eedb398832eeb7e8e0ceafd21 | | cvelistv5 | | | | https://git.kernel.org/stable/c/764c9f69beabef8bdc651a7746c59f7a340d104f | | cvelistv5 | | | | https://git.kernel.org/stable/c/fd960b5ddf4faf00da43babdd3acda68842e1f6a | | cvelistv5 | | | | https://git.kernel.org/stable/c/6883b680e703c6b2efddb4e7a8d891ce1803d06b | | cvelistv5 | | | | https://git.kernel.org/stable/c/23a707bbcbea468eedb398832eeb7e8e0ceafd21 | | snyk | | | | https://git.kernel.org/stable/c/3b4a50d733acad6831f6bd9288a76a80f70650ac | | snyk | | | | https://git.kernel.org/stable/c/6883b680e703c6b2efddb4e7a8d891ce1803d06b | | snyk | | | | https://git.kernel.org/stable/c/764c9f69beabef8bdc651a7746c59f7a340d104f | | snyk | | | | https://git.kernel.org/stable/c/78381dc8a6b61c9bb9987d37b4d671b99767c4a1 | | snyk | | | | https://git.kernel.org/stable/c/fd960b5ddf4faf00da43babdd3acda68842e1f6a | | snyk | | | | https://git.kernel.org/stable/c/013dcdf6f03bcedbaf1669e3db71c34a197715b2 | | snyk | | | | https://git.kernel.org/stable/c/bf7eff5e3a36c54bbe8aff7fd6dd7c07490b81c5 | | snyk | </details> 二、漏洞分析结构反馈 影响性分析说明： In the Linux kernel, the following vulnerability has been resolved:RDMA/iwcm: Fix use-after-free of work objects after cm_id destructionThe commit 59c68ac31e15 ("iw_cm: free cm_id resources on the lastderef") simplified cm_id resource management by freeing cm_id once allreferences to the cm_id were removed. The references are removed eitherupon completion of iw_cm event handlers or when the application destroysthe cm_id. This commit introduced the use-after-free condition wherecm_id_private object could still be in use by event handler works duringthe destruction of cm_id. The commit aee2424246f9 ("RDMA/iwcm: Fix ause-after-free related to destroying CM IDs") addressed this use-after-free by flushing all pending works at the cm_id destruction.However, still another use-after-free possibility remained. It happenswith the work objects allocated for each cm_id_priv withinalloc_work_entries() during cm_id creation, and subsequently freed indealloc_work_entries() once all references to the cm_id are removed.If the cm_id's last reference is decremented in the event handler work,the work object for the work itself gets removed, and causes the use-after-free BUG below: BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250 Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091 CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014 Workqueue: 0x0 (iw_cm_wq) Call Trace: <TASK> dump_stack_lvl+0x6a/0x90 print_report+0x174/0x554 ? __virt_addr_valid+0x208/0x430 ? __pwq_activate_work+0x1ff/0x250 kasan_report+0xae/0x170 ? __pwq_activate_work+0x1ff/0x250 __pwq_activate_work+0x1ff/0x250 pwq_dec_nr_in_flight+0x8c5/0xfb0 process_one_work+0xc11/0x1460 ? __pfx_process_one_work+0x10/0x10 ? assign_work+0x16c/0x240 worker_thread+0x5ef/0xfd0 ? __pfx_worker_thread+0x10/0x10 kthread+0x3b0/0x770 ? __pfx_kthread+0x10/0x10 ? rcu_is_watching+0x11/0xb0 ? _raw_spin_unlock_irq+0x24/0x50 ? rcu_is_watching+0x11/0xb0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x30/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 147416: kasan_save_stack+0x2c/0x50 kasan_save_track+0x10/0x30 __kasan_kmalloc+0xa6/0xb0 alloc_work_entries+0xa9/0x260 [iw_cm] iw_cm_connect+0x23/0x4a0 [iw_cm] rdma_connect_locked+0xbfd/0x1920 [rdma_cm] nvme_rdma_cm_handler+0x8e5/0x1b60 [nvme_rdma] cma_cm_event_handler+0xae/0x320 [rdma_cm] cma_work_handler+0x106/0x1b0 [rdma_cm] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30 Freed by task 147091: kasan_save_stack+0x2c/0x50 kasan_save_track+0x10/0x30 kasan_save_free_info+0x37/0x60 __kasan_slab_free+0x4b/0x70 kfree+0x13a/0x4b0 dealloc_work_entries+0x125/0x1f0 [iw_cm] iwcm_deref_id+0x6f/0xa0 [iw_cm] cm_work_handler+0x136/0x1ba0 [iw_cm] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30 Last potentially related work creation: kasan_save_stack+0x2c/0x50 kasan_record_aux_stack+0xa3/0xb0 __queue_work+0x2ff/0x1390 queue_work_on+0x67/0xc0 cm_event_handler+0x46a/0x820 [iw_cm] siw_cm_upcall+0x330/0x650 [siw] siw_cm_work_handler+0x6b9/0x2b20 [siw] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30This BUG is reproducible by repeating the blktests test case nvme/061for the rdma transport and the siw driver.To avoid the use-after-free of cm_id_private work objects, ensure thatthe last reference to the cm_id is decremented not in the event handlerworks, but in the cm_id destruction context. For that purpose, moveiwcm_deref_id() call from destroy_cm_id() to the callers ofdestroy_cm_id(). In iw_destroy_cm_id(), call iwcm_deref_id() afterflushing the pending works.During the fix work, I noticed t openEuler评分： 6.1 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/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.openEuler-24.03-LTS-SP2(6.6.0):受影响 7.master(6.12.33):不受影响 8.openEuler-24.03-LTS-Next(6.6.0):不受影响 修复是否涉及abi变化(是/否)： 1.master(6.12.33):否 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):否 8.openEuler-24.03-LTS-SP2(6.6.0):否 原因说明： 1.openEuler-24.03-LTS(6.6.0):正常修复 2.openEuler-24.03-LTS-SP1(6.6.0):正常修复 3.openEuler-24.03-LTS-SP2(6.6.0):正常修复 4.openEuler-20.03-LTS-SP4(4.19.90):不修复-超出修复范围 5.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围 6.openEuler-22.03-LTS-SP4(5.10.0):不修复-超出修复范围 7.master(6.12.33):不受影响-漏洞代码不能被攻击者触发 8.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发 三、漏洞修复 安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-2056
一、漏洞信息 漏洞编号：[CVE-2025-38211](https://nvd.nist.gov/vuln/detail/CVE-2025-38211) 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/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：N/A None Vector：CVSS：3.0/ 漏洞简述： A use-after-free vulnerability exists in the RDMA/iwcm component of the Linux kernel. The vulnerability occurs when work objects of cm_id_private are still in use by event handlers after cm_id destruction. While previous patches attempted to address this by flushing pending works, decrementing the last reference to cm_id within the event handler work leads to removal of the work object itself, triggering the use-after-free BUG. 漏洞公开时间：2025-07-04 22:15:29 漏洞创建时间：2025-07-04 23:01:54 漏洞详情参考链接： https://nvd.nist.gov/vuln/detail/CVE-2025-38211 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | | https://git.kernel.org/stable/c/23a707bbcbea468eedb398832eeb7e8e0ceafd21 | | | | https://git.kernel.org/stable/c/3b4a50d733acad6831f6bd9288a76a80f70650ac | | | | https://git.kernel.org/stable/c/6883b680e703c6b2efddb4e7a8d891ce1803d06b | | | | https://git.kernel.org/stable/c/764c9f69beabef8bdc651a7746c59f7a340d104f | | | | https://git.kernel.org/stable/c/78381dc8a6b61c9bb9987d37b4d671b99767c4a1 | | | | https://git.kernel.org/stable/c/fd960b5ddf4faf00da43babdd3acda68842e1f6a | | | | https://security-tracker.debian.org/tracker/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | | | https://access.redhat.com/security/cve/CVE-2025-38211 | | </details> 漏洞分析指导链接： https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: 七彩瞬析开源风险感知平台 漏洞补丁信息： <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | gregkh/linux | | https://github.com/gregkh/linux/commit/23a707bbcbea468eedb398832eeb7e8e0ceafd21.patch | | ljqc | | | | https://git.kernel.org/stable/c/23a707bbcbea468eedb398832eeb7e8e0ceafd21 | | nvd | | | | https://git.kernel.org/stable/c/3b4a50d733acad6831f6bd9288a76a80f70650ac | | nvd | | | | https://git.kernel.org/stable/c/6883b680e703c6b2efddb4e7a8d891ce1803d06b | | nvd | | | | https://git.kernel.org/stable/c/764c9f69beabef8bdc651a7746c59f7a340d104f | | nvd | | | | https://git.kernel.org/stable/c/78381dc8a6b61c9bb9987d37b4d671b99767c4a1 | | nvd | | | | https://git.kernel.org/stable/c/fd960b5ddf4faf00da43babdd3acda68842e1f6a | | nvd | | | | https://git.kernel.org/stable/c/013dcdf6f03bcedbaf1669e3db71c34a197715b2 | | nvd | | | | https://git.kernel.org/stable/c/bf7eff5e3a36c54bbe8aff7fd6dd7c07490b81c5 | | nvd | | | | https://git.kernel.org/stable/c/013dcdf6f03bcedbaf1669e3db71c34a197715b2 | | cvelistv5 | | | | https://git.kernel.org/stable/c/bf7eff5e3a36c54bbe8aff7fd6dd7c07490b81c5 | | cvelistv5 | | | | https://git.kernel.org/stable/c/3b4a50d733acad6831f6bd9288a76a80f70650ac | | cvelistv5 | | | | https://git.kernel.org/stable/c/78381dc8a6b61c9bb9987d37b4d671b99767c4a1 | | cvelistv5 | | | | https://git.kernel.org/stable/c/23a707bbcbea468eedb398832eeb7e8e0ceafd21 | | cvelistv5 | | | | https://git.kernel.org/stable/c/764c9f69beabef8bdc651a7746c59f7a340d104f | | cvelistv5 | | | | https://git.kernel.org/stable/c/fd960b5ddf4faf00da43babdd3acda68842e1f6a | | cvelistv5 | | | | https://git.kernel.org/stable/c/6883b680e703c6b2efddb4e7a8d891ce1803d06b | | cvelistv5 | | | | https://git.kernel.org/stable/c/23a707bbcbea468eedb398832eeb7e8e0ceafd21 | | snyk | | | | https://git.kernel.org/stable/c/3b4a50d733acad6831f6bd9288a76a80f70650ac | | snyk | | | | https://git.kernel.org/stable/c/6883b680e703c6b2efddb4e7a8d891ce1803d06b | | snyk | | | | https://git.kernel.org/stable/c/764c9f69beabef8bdc651a7746c59f7a340d104f | | snyk | | | | https://git.kernel.org/stable/c/78381dc8a6b61c9bb9987d37b4d671b99767c4a1 | | snyk | | | | https://git.kernel.org/stable/c/fd960b5ddf4faf00da43babdd3acda68842e1f6a | | snyk | | | | https://git.kernel.org/stable/c/013dcdf6f03bcedbaf1669e3db71c34a197715b2 | | snyk | | | | https://git.kernel.org/stable/c/bf7eff5e3a36c54bbe8aff7fd6dd7c07490b81c5 | | snyk | </details> 二、漏洞分析结构反馈 影响性分析说明： In the Linux kernel, the following vulnerability has been resolved:RDMA/iwcm: Fix use-after-free of work objects after cm_id destructionThe commit 59c68ac31e15 ("iw_cm: free cm_id resources on the lastderef") simplified cm_id resource management by freeing cm_id once allreferences to the cm_id were removed. The references are removed eitherupon completion of iw_cm event handlers or when the application destroysthe cm_id. This commit introduced the use-after-free condition wherecm_id_private object could still be in use by event handler works duringthe destruction of cm_id. The commit aee2424246f9 ("RDMA/iwcm: Fix ause-after-free related to destroying CM IDs") addressed this use-after-free by flushing all pending works at the cm_id destruction.However, still another use-after-free possibility remained. It happenswith the work objects allocated for each cm_id_priv withinalloc_work_entries() during cm_id creation, and subsequently freed indealloc_work_entries() once all references to the cm_id are removed.If the cm_id's last reference is decremented in the event handler work,the work object for the work itself gets removed, and causes the use-after-free BUG below: BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250 Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091 CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014 Workqueue: 0x0 (iw_cm_wq) Call Trace: <TASK> dump_stack_lvl+0x6a/0x90 print_report+0x174/0x554 ? __virt_addr_valid+0x208/0x430 ? __pwq_activate_work+0x1ff/0x250 kasan_report+0xae/0x170 ? __pwq_activate_work+0x1ff/0x250 __pwq_activate_work+0x1ff/0x250 pwq_dec_nr_in_flight+0x8c5/0xfb0 process_one_work+0xc11/0x1460 ? __pfx_process_one_work+0x10/0x10 ? assign_work+0x16c/0x240 worker_thread+0x5ef/0xfd0 ? __pfx_worker_thread+0x10/0x10 kthread+0x3b0/0x770 ? __pfx_kthread+0x10/0x10 ? rcu_is_watching+0x11/0xb0 ? _raw_spin_unlock_irq+0x24/0x50 ? rcu_is_watching+0x11/0xb0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x30/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 147416: kasan_save_stack+0x2c/0x50 kasan_save_track+0x10/0x30 __kasan_kmalloc+0xa6/0xb0 alloc_work_entries+0xa9/0x260 [iw_cm] iw_cm_connect+0x23/0x4a0 [iw_cm] rdma_connect_locked+0xbfd/0x1920 [rdma_cm] nvme_rdma_cm_handler+0x8e5/0x1b60 [nvme_rdma] cma_cm_event_handler+0xae/0x320 [rdma_cm] cma_work_handler+0x106/0x1b0 [rdma_cm] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30 Freed by task 147091: kasan_save_stack+0x2c/0x50 kasan_save_track+0x10/0x30 kasan_save_free_info+0x37/0x60 __kasan_slab_free+0x4b/0x70 kfree+0x13a/0x4b0 dealloc_work_entries+0x125/0x1f0 [iw_cm] iwcm_deref_id+0x6f/0xa0 [iw_cm] cm_work_handler+0x136/0x1ba0 [iw_cm] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30 Last potentially related work creation: kasan_save_stack+0x2c/0x50 kasan_record_aux_stack+0xa3/0xb0 __queue_work+0x2ff/0x1390 queue_work_on+0x67/0xc0 cm_event_handler+0x46a/0x820 [iw_cm] siw_cm_upcall+0x330/0x650 [siw] siw_cm_work_handler+0x6b9/0x2b20 [siw] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30This BUG is reproducible by repeating the blktests test case nvme/061for the rdma transport and the siw driver.To avoid the use-after-free of cm_id_private work objects, ensure thatthe last reference to the cm_id is decremented not in the event handlerworks, but in the cm_id destruction context. For that purpose, moveiwcm_deref_id() call from destroy_cm_id() to the callers ofdestroy_cm_id(). In iw_destroy_cm_id(), call iwcm_deref_id() afterflushing the pending works.During the fix work, I noticed t openEuler评分： 6.1 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/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.openEuler-24.03-LTS-SP2(6.6.0):受影响 7.master(6.12.33):不受影响 8.openEuler-24.03-LTS-Next(6.6.0):不受影响 修复是否涉及abi变化(是/否)： 1.master(6.12.33):否 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):否 8.openEuler-24.03-LTS-SP2(6.6.0):否 原因说明： 1.openEuler-24.03-LTS(6.6.0):正常修复 2.openEuler-24.03-LTS-SP1(6.6.0):正常修复 3.openEuler-24.03-LTS-SP2(6.6.0):正常修复 4.openEuler-20.03-LTS-SP4(4.19.90):不修复-超出修复范围 5.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围 6.openEuler-22.03-LTS-SP4(5.10.0):不修复-超出修复范围 7.master(6.12.33):不受影响-漏洞代码不能被攻击者触发 8.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发 三、漏洞修复 安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-2056
评论 (
13
)
登录
后才可以发表评论
状态
已完成
待办的
已挂起
进行中
已完成
已拒绝
负责人
未设置
CTC-Xibo.Wang
CTC-XiboWang
负责人
协作者
+负责人
+协作者
标签
CVE/FIXED
sig/Kernel
未设置
项目
未立项任务
未立项任务
里程碑
未关联里程碑
未关联里程碑
Pull Requests
未关联
未关联
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
未关联
分支 (37)
标签 (229)
master
openEuler-24.03-LTS-SP2
openEuler-24.03-LTS-SP1
openEuler-24.03-LTS
openEuler-22.03-LTS-SP4
openEuler-22.03-LTS-SP3
openEuler-20.03-LTS-SP4
openEuler-25.09
openEuler-24.03-LTS-Next
openEuler-25.03
openEuler-22.03-LTS-SP2
openEuler-22.03-LTS-SP1
openEuler-22.03-LTS-SP4-64KB
openEuler-24.09
openEuler-22.03-LTS-Next
openEuler-24.03-LTS-Loongarch
openEuler-22.03-LTS
openEuler-20.03-LTS-SP1
sync-pr1519-openEuler-24.03-LTS-to-openEuler-24.03-LTS-Next
sync-pr1486-master-to-openEuler-24.03-LTS-Next
loongarch-support
openEuler-20.03-LTS-SP3
sync-pr1314-openEuler-22.03-LTS-SP3-to-openEuler-22.03-LTS-Next
openEuler-23.09
openEuler-23.03
openEuler-22.03-LTS-LoongArch
openEuler-22.09
openEuler-22.09-HeXin
openEuler-20.03-LTS-SP2
openEuler-21.09
openEuler-20.03-LTS
openEuler-20.03-LTS-Next
openEuler-21.03
openEuler-20.09
openEuler-20.03-LTS-SP1-testing
openEuler1.0
openEuler1.0-base
openEuler-20.03-LTS-SP4-update-20250829
openEuler-22.03-LTS-SP4-update-20250829
openEuler-24.03-LTS-SP1-update-20250829
openEuler-24.03-LTS-update-20250829
openEuler-24.03-LTS-SP2-update-20250829
openEuler-22.03-LTS-SP3-update-20250822
openEuler-22.03-LTS-SP4-update-20250822
openEuler-24.03-LTS-update-20250822
openEuler-24.03-LTS-SP1-update-20250822
openEuler-24.03-LTS-SP2-update-20250822
openEuler-22.03-LTS-SP4-update-20250815
openEuler-22.03-LTS-SP3-update-20250815
openEuler-24.03-LTS-SP2-update-20250815
openEuler-20.03-LTS-SP4-update-20250815
openEuler-24.03-LTS-update-20250815
openEuler-24.03-LTS-SP1-update-20250815
openEuler-20.03-LTS-SP4-update-20250808
openEuler-22.03-LTS-SP3-update-20250808
openEuler-22.03-LTS-SP4-update-20250808
openEuler-24.03-LTS-update-20250808
openEuler-24.03-LTS-SP1-update-20250808
openEuler-24.03-LTS-SP2-update-20250808
openEuler-22.03-LTS-SP3-update-20250801
openEuler-22.03-LTS-SP4-update-20250801
openEuler-24.03-LTS-update-20250801
openEuler-24.03-LTS-SP1-update-20250801
openEuler-24.03-LTS-SP2-update-20250801
openEuler-20.03-LTS-SP4-update-20250725
openEuler-22.03-LTS-SP3-update-20250725
openEuler-22.03-LTS-SP4-update-20250725
openEuler-24.03-LTS-update-20250725
openEuler-24.03-LTS-SP1-update-20250725
openEuler-24.03-LTS-SP2-update-20250725
openEuler-20.03-LTS-SP4-update-20250718
openEuler-22.03-LTS-SP3-update-20250718
openEuler-22.03-LTS-SP4-update-20250718
openEuler-24.03-LTS-update-20250718
openEuler-24.03-LTS-SP1-update-20250718
openEuler-24.03-LTS-SP2-update-20250718
openEuler-20.03-LTS-SP4-update-20250711
openEuler-22.03-LTS-SP3-update-20250711
openEuler-22.03-LTS-SP4-update-20250711
openEuler-24.03-LTS-update-20250711
openEuler-24.03-LTS-SP1-update-20250711
openEuler-20.03-LTS-SP4-update-20250704
openEuler-22.03-LTS-SP3-update-20250704
openEuler-22.03-LTS-SP4-update-20250704
openEuler-24.03-LTS-update-20250704
openEuler-24.03-LTS-SP1-update-20250704
openEuler-20.03-LTS-SP4-update-20250627
openEuler-22.03-LTS-SP3-update-20250627
openEuler-22.03-LTS-SP4-update-20250627
openEuler-20.03-LTS-SP4-update-20250620
openEuler-22.03-LTS-SP3-update-20250620
openEuler-22.03-LTS-SP4-update-20250620
openEuler-24.03-LTS-update-20250620
openEuler-24.03-LTS-SP1-update-20250620
openEuler-24.03-LTS-SP2-release
openEuler-20.03-LTS-SP4-update-20250613
openEuler-22.03-LTS-SP3-update-20250613
openEuler-22.03-LTS-SP4-update-20250613
openEuler-24.03-LTS-update-20250613
openEuler-24.03-LTS-SP1-update-20250613
openEuler-20.03-LTS-SP4-update-20250606
openEuler-22.03-LTS-SP3-update-20250606
openEuler-22.03-LTS-SP4-update-20250606
openEuler-24.03-LTS-update-20250606
openEuler-24.03-LTS-SP1-update-20250606
openEuler-20.03-LTS-SP4-update-20250530
openEuler-22.03-LTS-SP3-update-20250530
openEuler-22.03-LTS-SP4-update-20250530
openEuler-24.03-LTS-update-20250530
openEuler-24.03-LTS-SP1-update-20250530
openEuler-20.03-LTS-SP4-update-20250523
openEuler-24.03-LTS-update-20250523
openEuler-24.03-LTS-SP1-update-20250523
openEuler-24.03-LTS-SP1-update-20250516
openEuler-24.03-LTS-update-20250516
openEuler-22.03-LTS-SP4-update-20250516
openEuler-22.03-LTS-SP3-update-20250516
openEuler-20.03-LTS-SP4-update-20250516
openEuler-24.03-LTS-SP1-update-20250509
openEuler-24.03-LTS-update-20250509
openEuler-22.03-LTS-SP4-update-20250509
openEuler-22.03-LTS-SP3-update-20250509
openEuler-20.03-LTS-SP4-update-20250509
openEuler-24.03-LTS-update-20250425
openEuler-22.03-LTS-SP3-update-20250425
openEuler-24.03-LTS-SP1-update-20250425
openEuler-24.03-LTS-SP1-update-20250428
openEuler-22.03-LTS-SP4-update-20250425
openEuler-20.03-LTS-SP4-update-20250425
openEuler-22.03-LTS-SP3-update-20250418
openEuler-22.03-LTS-SP4-update-20250418
openEuler-20.03-LTS-SP4-update-20250418
openEuler-22.03-LTS-SP3-update-20250411
openEuler-22.03-LTS-SP4-update-20250411
openEuler-20.03-LTS-SP4-update-20250411
openEuler-20.03-LTS-SP4-update-20250403
openEuler-24.03-LTS-SP1-update-20250403
openEuler-24.03-LTS-update-20250403
openEuler-25.03-release
openEuler-20.03-LTS-SP4-update-20250329
openEuler-22.03-LTS-SP4-update-20250329
openEuler-22.03-LTS-SP3-update-20250329
openEuler-24.03-LTS-SP1-update-20250329
openEuler-24.03-LTS-update-20250329
openEuler-24.03-LTS-update-20250321
openEuler-24.03-LTS-SP1-update-20250321
openEuler-20.03-LTS-SP4-update-20250321
openEuler-24.03-LTS-update-20250314
openEuler-24.03-LTS-SP1-update-20250314
openEuler-22.03-LTS-SP3-update-20250314
openEuler-22.03-LTS-SP4-update-20250314
openEuler-20.03-LTS-SP4-update-20250314
openEuler-24.03-LTS-update-20250307
openEuler-24.03-LTS-SP1-update-20250307
openEuler-22.03-LTS-SP3-update-20250307
openEuler-22.03-LTS-SP4-update-20250307
openEuler-20.03-LTS-SP4-update-20250307
openEuler-24.03-LTS-update-20250228
openEuler-24.03-LTS-SP1-update-20250228
openEuler-22.03-LTS-SP3-update-20250228
openEuler-22.03-LTS-SP4-update-20250228
openEuler-20.03-LTS-SP4-update-20250228
openEuler-24.03-LTS-SP1-update-20250221
openEuler-24.03-LTS-update-20250221
openEuler-22.03-LTS-SP4-update-20250221
openEuler-22.03-LTS-SP3-update-20250221
openEuler-20.03-LTS-SP4-update-20250221
openEuler-24.03-LTS-update-20250214
openEuler-24.03-LTS-SP1-update-20250214
openEuler-22.03-LTS-SP4-update-20250214
openEuler-22.03-LTS-SP3-update-20250214
openEuler-20.03-LTS-SP4-update-20250214
openEuler-24.03-LTS-update-20250208
openEuler-20.03-LTS-SP4-update-20250208
openEuler-22.03-LTS-SP3-update-20250208
openEuler-22.03-LTS-SP4-update-20250208
openEuler-24.03-LTS-SP1-update-20250208
openEuler-24.03-LTS-SP1-update-20250124
openEuler-22.03-LTS-SP4-update-20250124
openEuler-22.03-LTS-SP3-update-20250124
openEuler-20.03-LTS-SP4-update-20250124
openEuler-24.03-LTS-update-20250124
openEuler-22.03-LTS-SP3-update-20250117
openEuler-22.03-LTS-SP4-update-20250117
openEuler-20.03-LTS-SP4-update-20250117
openEuler-24.03-LTS-update-20250110
openEuler-24.03-LTS-SP1-update-20250110
openEuler-22.03-LTS-SP1-update-20250110
openEuler-22.03-LTS-SP3-update-20250110
openEuler-20.03-LTS-SP4-update-20250110
openEuler-22.03-LTS-SP4-update-20250110
openEuler-22.03-LTS-SP4-update-20250103
openEuler-22.03-LTS-SP3-update-20250103
openEuler-22.03-LTS-SP1-update-20250103
openEuler-20.03-LTS-SP4-update-20250103
openEuler-24.03-LTS-SP1-release
openEuler-24.03-LTS-update-20241227
openEuler-22.03-LTS-SP3-update-20241227
openEuler-22.03-LTS-SP4-update-20241227
openEuler-20.03-LTS-SP4-update-20241227
openEuler-22.03-LTS-SP4-update-20241220
openEuler-22.03-LTS-SP3-update-20241220
openEuler-20.03-LTS-SP4-update-20241220
openEuler-24.03-LTS-update-20241213
openEuler-22.03-LTS-SP4-update-20241213
openEuler-22.03-LTS-SP3-update-20241213
openEuler-22.03-LTS-SP1-update-20241213
openEuler-20.03-LTS-SP4-update-20241213
openEuler-24.03-LTS-update-20241206
openEuler-22.03-LTS-SP4-update-20241206
openEuler-22.03-LTS-SP3-update-20241206
openEuler-22.03-LTS-SP1-update-20241206
openEuler-20.03-LTS-SP4-update-20241206
openEuler-20.03-LTS-SP4-update-20241129
openEuler-22.03-LTS-SP1-update-20241129
openEuler-22.03-LTS-SP3-update-20241129
openEuler-22.03-LTS-SP4-update-20241129
openEuler-24.03-LTS-update-20241129
openEuler-24.03-LTS-update-20241122
openEuler-22.03-LTS-SP4-update-20241122
openEuler-22.03-LTS-SP3-update-20241122
openEuler-22.03-LTS-SP1-update-20241122
openEuler-20.03-LTS-SP4-update-20241122
openEuler-20.03-LTS-SP4-update-20241115
openEuler-22.03-LTS-SP1-update-20241115
openEuler-22.03-LTS-SP3-update-20241115
openEuler-22.03-LTS-SP4-update-20241115
openEuler-24.03-LTS-update-20241115
openEuler-24.03-LTS-update-20241108
openEuler-22.03-LTS-SP4-update-20241108
openEuler-22.03-LTS-SP3-update-20241108
openEuler-22.03-LTS-SP1-update-20241108
openEuler-20.03-LTS-SP4-update-20241108
openEuler-22.03-LTS-SP4-update-before-20241025
openEuler-22.03-LTS-SP4-before-20241025
openEuler-24.03-LTS-update-before-20241025
openEuler-20.03-LTS-SP4-update-20241101
openEuler-22.03-LTS-SP1-update-20241101
openEuler-22.03-LTS-SP3-update-20241101
openEuler-22.03-LTS-SP4-update-20241101
openEuler-24.03-LTS-update-20241101
openEuler-20.03-LTS-SP4-update-20241025
openEuler-22.03-LTS-SP1-update-20241025
openEuler-22.03-LTS-SP3-update-20241025
openEuler-22.03-LTS-SP4-update-20241025
openEuler-24.03-LTS-update-20241025
openEuler-22.03-LTS-SP4-release
openEuler-24.09-release
openEuler-24.03-LTS-release
openEuler-22.03-LTS-SP3-release
openEuler-23.09-rc5
openEuler-22.03-LTS-SP1-release
openEuler-22.09-release
openEuler-22.09-rc5
openEuler-22.09-20220829
openEuler-22.03-LTS-20220331
openEuler-22.03-LTS-round5
openEuler-22.03-LTS-round3
openEuler-22.03-LTS-round2
openEuler-22.03-LTS-round1
openEuler-20.03-LTS-SP3-release
openEuler-20.03-LTS-SP2-20210624
openEuler-21.03-20210330
openEuler-20.09-20200929
openEuler-20.03-LTS-20200606
openEuler-20.03-LTS-tag
开始日期 - 截止日期
-
置顶选项
不置顶
置顶等级：高
置顶等级：中
置顶等级：低
优先级
不指定
严重
主要
次要
不重要
预计工期
（小时）
参与者（1）
1
https://gitee.com/src-openeuler/kernel.git
git@gitee.com:src-openeuler/kernel.git
src-openeuler
kernel
kernel
点此查找更多帮助
搜索帮助
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大，如何减小？
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release（发行版）
将 PHP 项目自动发布到 packagist.org
仓库举报
回到顶部
登录提示
该操作需登录 Gitee 帐号，请先登录后再操作。
立即登录
没有帐号，去注册
