登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
模力方舟
AI 队友
登录
注册
代码拉取完成,页面将自动刷新
开源项目
>
其他开源
>
操作系统
&&
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
113
Star
72
Fork
323
src-openEuler
/
kernel
代码
Issues
1281
Pull Requests
38
Wiki
统计
流水线
服务
JavaDoc
PHPDoc
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
SBOM
我知道了,不再自动展开
更新失败,请稍后重试!
移除标识
内容风险标识
本任务被
标识为内容中包含有代码安全 Bug 、隐私泄露等敏感信息,仓库外成员不可访问
CVE-2023-52743
已完成
#I9R4N2
CVE和安全问题
openeuler-ci-bot
拥有者
创建于
2024-05-22 03:00
一、漏洞信息 漏洞编号:[CVE-2023-52743](https://nvd.nist.gov/vuln/detail/CVE-2023-52743) 漏洞归属组件:[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0 CVSS V2.0分值: BaseScore:0.0 Medium Vector:CVSS:2.0/ 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:ice: Do not use WQ_MEM_RECLAIM flag for workqueueWhen both ice and the irdma driver are loaded, a warning incheck_flush_dependency is being triggered. This is due to ice driverworkqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma oneis not.According to kernel documentation, this flag should be set if theworkqueue will be involved in the kernel s memory reclamation flow.Since it is not, there is no need for the ice driver s WQ to have thisflag set so remove it.Example trace:[ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0[ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2632 check_flush_dependency+0x178/0x1a0[ +0.000011] Modules linked in: bonding tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc rfkill vfat fat intel_rapl_msr intel_rapl_common isst_if_common skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel rapl intel_cstate rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_core_mod ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_cm iw_cm iTCO_wdt iTCO_vendor_support ipmi_ssif irdma mei_me ib_uverbsib_core intel_uncore joydev pcspkr i2c_i801 acpi_ipmi mei lpc_ich i2c_smbus intel_pch_thermal ioatdma ipmi_si acpi_power_meteracpi_pad xfs libcrc32c sd_mod t10_pi crc64_rocksoft crc64 sg ahci ixgbe libahci ice i40e igb crc32c_intel mdio i2c_algo_bit libata dca wmi dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse[ +0.000161] [last unloaded: bonding][ +0.000006] CPU: 0 PID: 728 Comm: kworker/0:2 Tainted: G S 6.2.0-rc2_next-queue-13jan-00458-gc20aabd57164 #1[ +0.000006] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0010.010620200716 01/06/2020[ +0.000003] Workqueue: ice ice_service_task [ice][ +0.000127] RIP: 0010:check_flush_dependency+0x178/0x1a0[ +0.000005] Code: 89 8e 02 01 e8 49 3d 40 00 49 8b 55 18 48 8d 8d d0 00 00 00 48 8d b3 d0 00 00 00 4d 89 e0 48 c7 c7 e0 3b 089f e8 bb d3 07 01 <0f> 0b e9 be fe ff ff 80 3d 24 89 8e 02 00 0f 85 6b ff ff ff e9 06[ +0.000004] RSP: 0018:ffff88810a39f990 EFLAGS: 00010282[ +0.000005] RAX: 0000000000000000 RBX: ffff888141bc2400 RCX: 0000000000000000[ +0.000004] RDX: 0000000000000001 RSI: dffffc0000000000 RDI: ffffffffa1213a80[ +0.000003] RBP: ffff888194bf3400 R08: ffffed117b306112 R09: ffffed117b306112[ +0.000003] R10: ffff888bd983088b R11: ffffed117b306111 R12: 0000000000000000[ +0.000003] R13: ffff888111f84d00 R14: ffff88810a3943ac R15: ffff888194bf3400[ +0.000004] FS: 0000000000000000(0000) GS:ffff888bd9800000(0000) knlGS:0000000000000000[ +0.000003] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033[ +0.000003] CR2: 000056035b208b60 CR3: 000000017795e005 CR4: 00000000007706f0[ +0.000003] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000[ +0.000003] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400[ +0.000002] PKRU: 55555554[ +0.000003] Call Trace:[ +0.000002] <TASK>[ +0.000003] __flush_workqueue+0x203/0x840[ +0.000006] ? mutex_unlock+0x84/0xd0[ +0.000008] ? __pfx_mutex_unlock+0x10/0x10[ +0.000004] ? __pfx___flush_workqueue+0x10/0x10[ +0.000006] ? mutex_lock+0xa3/0xf0[ +0.000005] ib_cache_cleanup_one+0x39/0x190 [ib_core][ +0.000174] __ib_unregister_device+0x84/0xf0 [ib_core][ +0.000094] ib_unregister_device+0x25/0x30 [ib_core][ +0.000093] irdma_ib_unregister_device+0x97/0xc0 [irdma][ +0.000064] ? __pfx_irdma_ib_unregister_device+0x10/0x10 [irdma][ +0.000059] ? up_write+0x5c/0x90[ +0.000005] irdma_remove+0x36/0x90 [irdma][ +0.000062] auxiliary_bus_remove+0x32/0x50[ +0.000007] device_r---truncated--- 漏洞公开时间:2024-05-22 00:15:14 漏洞创建时间:2024-05-22 03:00:55 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2023-52743 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/1ad4112c9fcf0bc08222b2b1614fba52ffd12255 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/87a5e3fc8416106e290c448fc8a6dd50ab24c634 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ca834a017851c50464c25a85f3cb2daefff7bede | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/df59e05401450973c8c7e96fd74b49e24442dc1f | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52743 | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2023/CVE-2023-52743.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/stable/c/87a5e3fc8416106e290c448fc8a6dd50ab24c634 | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/stable/c/1ad4112c9fcf0bc08222b2b1614fba52ffd12255 | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/stable/c/ca834a017851c50464c25a85f3cb2daefff7bede | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/stable/c/df59e05401450973c8c7e96fd74b49e24442dc1f | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/stable/c/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2023-52743 | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024052102-CVE-2023-52743-f027@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2282788 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2023-52743 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/linus/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 (6.2-rc8) | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/stable/c/87a5e3fc8416106e290c448fc8a6dd50ab24c634 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/stable/c/1ad4112c9fcf0bc08222b2b1614fba52ffd12255 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/stable/c/ca834a017851c50464c25a85f3cb2daefff7bede | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/stable/c/df59e05401450973c8c7e96fd74b49e24442dc1f | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/stable/c/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2023-52743 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2023-52743 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2023-52743 | https://ubuntu.com/security/CVE-2023-52743 | | debian | | https://security-tracker.debian.org/tracker/CVE-2023-52743 | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | linux | | https://git.kernel.org/linus/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 | https://git.kernel.org/linus/940b61af02f497fcd911b9e2d75c6b8cf76b92fd | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:ice: Do not use WQ_MEM_RECLAIM flag for workqueueWhen both ice and the irdma driver are loaded, a warning incheck_flush_dependency is being triggered. This is due to ice driverworkqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma oneis not.According to kernel documentation, this flag should be set if theworkqueue will be involved in the kernel s memory reclamation flow.Since it is not, there is no need for the ice driver s WQ to have thisflag set so remove it.Example trace:[ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0[ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2632 check_flush_dependency+0x178/0x1a0[ +0.000011] Modules linked in: bonding tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc rfkill vfat fat intel_rapl_msr intel_rapl_common isst_if_common skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel rapl intel_cstate rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_core_mod ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_cm iw_cm iTCO_wdt iTCO_vendor_support ipmi_ssif irdma mei_me ib_uverbsib_core intel_uncore joydev pcspkr i2c_i801 acpi_ipmi mei lpc_ich i2c_smbus intel_pch_thermal ioatdma ipmi_si acpi_power_meteracpi_pad xfs libcrc32c sd_mod t10_pi crc64_rocksoft crc64 sg ahci ixgbe libahci ice i40e igb crc32c_intel mdio i2c_algo_bit libata dca wmi dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse[ +0.000161] [last unloaded: bonding][ +0.000006] CPU: 0 PID: 728 Comm: kworker/0:2 Tainted: G S 6.2.0-rc2_next-queue-13jan-00458-gc20aabd57164 #1[ +0.000006] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0010.010620200716 01/06/2020[ +0.000003] Workqueue: ice ice_service_task [ice][ +0.000127] RIP: 0010:check_flush_dependency+0x178/0x1a0[ +0.000005] Code: 89 8e 02 01 e8 49 3d 40 00 49 8b 55 18 48 8d 8d d0 00 00 00 48 8d b3 d0 00 00 00 4d 89 e0 48 c7 c7 e0 3b 089f e8 bb d3 07 01 <0f> 0b e9 be fe ff ff 80 3d 24 89 8e 02 00 0f 85 6b ff ff ff e9 06[ +0.000004] RSP: 0018:ffff88810a39f990 EFLAGS: 00010282[ +0.000005] RAX: 0000000000000000 RBX: ffff888141bc2400 RCX: 0000000000000000[ +0.000004] RDX: 0000000000000001 RSI: dffffc0000000000 RDI: ffffffffa1213a80[ +0.000003] RBP: ffff888194bf3400 R08: ffffed117b306112 R09: ffffed117b306112[ +0.000003] R10: ffff888bd983088b R11: ffffed117b306111 R12: 0000000000000000[ +0.000003] R13: ffff888111f84d00 R14: ffff88810a3943ac R15: ffff888194bf3400[ +0.000004] FS: 0000000000000000(0000) GS:ffff888bd9800000(0000) knlGS:0000000000000000[ +0.000003] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033[ +0.000003] CR2: 000056035b208b60 CR3: 000000017795e005 CR4: 00000000007706f0[ +0.000003] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000[ +0.000003] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400[ +0.000002] PKRU: 55555554[ +0.000003] Call Trace:[ +0.000002] <TASK>[ +0.000003] __flush_workqueue+0x203/0x840[ +0.000006] ? mutex_unlock+0x84/0xd0[ +0.000008] ? __pfx_mutex_unlock+0x10/0x10[ +0.000004] ? __pfx___flush_workqueue+0x10/0x10[ +0.000006] ? mutex_lock+0xa3/0xf0[ +0.000005] ib_cache_cleanup_one+0x39/0x190 [ib_core][ +0.000174] __ib_unregister_device+0x84/0xf0 [ib_core][ +0.000094] ib_unregister_device+0x25/0x30 [ib_core][ +0.000093] irdma_ib_unregister_device+0x97/0xc0 [irdma][ +0.000064] ? __pfx_irdma_ib_unregister_device+0x10/0x10 [irdma][ +0.000059] ? up_write+0x5c/0x90[ +0.000005] irdma_remove+0x36/0x90 [irdma][ +0.000062] auxiliary_bus_remove+0x32/0x50[ +0.000007] device_r---truncated--- openEuler评分: 4.0 Vector:CVSS:2.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L 受影响版本排查(受影响/不受影响): 1.openEuler-22.03-LTS-SP1(5.10.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.master(6.1.0):不受影响 6.openEuler-24.03-LTS(6.6.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-SP1(5.10.0):否 3.openEuler-22.03-LTS-SP3(5.10.0):否 4.master(6.1.0):否 5.openEuler-24.03-LTS(6.6.0):否 6.openEuler-24.03-LTS-Next(6.6.0):否 7.openEuler-22.03-LTS-SP4(5.10.0):否 三、漏洞修复 安全公告链接:https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-1860
一、漏洞信息 漏洞编号:[CVE-2023-52743](https://nvd.nist.gov/vuln/detail/CVE-2023-52743) 漏洞归属组件:[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0 CVSS V2.0分值: BaseScore:0.0 Medium Vector:CVSS:2.0/ 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:ice: Do not use WQ_MEM_RECLAIM flag for workqueueWhen both ice and the irdma driver are loaded, a warning incheck_flush_dependency is being triggered. This is due to ice driverworkqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma oneis not.According to kernel documentation, this flag should be set if theworkqueue will be involved in the kernel s memory reclamation flow.Since it is not, there is no need for the ice driver s WQ to have thisflag set so remove it.Example trace:[ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0[ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2632 check_flush_dependency+0x178/0x1a0[ +0.000011] Modules linked in: bonding tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc rfkill vfat fat intel_rapl_msr intel_rapl_common isst_if_common skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel rapl intel_cstate rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_core_mod ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_cm iw_cm iTCO_wdt iTCO_vendor_support ipmi_ssif irdma mei_me ib_uverbsib_core intel_uncore joydev pcspkr i2c_i801 acpi_ipmi mei lpc_ich i2c_smbus intel_pch_thermal ioatdma ipmi_si acpi_power_meteracpi_pad xfs libcrc32c sd_mod t10_pi crc64_rocksoft crc64 sg ahci ixgbe libahci ice i40e igb crc32c_intel mdio i2c_algo_bit libata dca wmi dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse[ +0.000161] [last unloaded: bonding][ +0.000006] CPU: 0 PID: 728 Comm: kworker/0:2 Tainted: G S 6.2.0-rc2_next-queue-13jan-00458-gc20aabd57164 #1[ +0.000006] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0010.010620200716 01/06/2020[ +0.000003] Workqueue: ice ice_service_task [ice][ +0.000127] RIP: 0010:check_flush_dependency+0x178/0x1a0[ +0.000005] Code: 89 8e 02 01 e8 49 3d 40 00 49 8b 55 18 48 8d 8d d0 00 00 00 48 8d b3 d0 00 00 00 4d 89 e0 48 c7 c7 e0 3b 089f e8 bb d3 07 01 <0f> 0b e9 be fe ff ff 80 3d 24 89 8e 02 00 0f 85 6b ff ff ff e9 06[ +0.000004] RSP: 0018:ffff88810a39f990 EFLAGS: 00010282[ +0.000005] RAX: 0000000000000000 RBX: ffff888141bc2400 RCX: 0000000000000000[ +0.000004] RDX: 0000000000000001 RSI: dffffc0000000000 RDI: ffffffffa1213a80[ +0.000003] RBP: ffff888194bf3400 R08: ffffed117b306112 R09: ffffed117b306112[ +0.000003] R10: ffff888bd983088b R11: ffffed117b306111 R12: 0000000000000000[ +0.000003] R13: ffff888111f84d00 R14: ffff88810a3943ac R15: ffff888194bf3400[ +0.000004] FS: 0000000000000000(0000) GS:ffff888bd9800000(0000) knlGS:0000000000000000[ +0.000003] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033[ +0.000003] CR2: 000056035b208b60 CR3: 000000017795e005 CR4: 00000000007706f0[ +0.000003] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000[ +0.000003] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400[ +0.000002] PKRU: 55555554[ +0.000003] Call Trace:[ +0.000002] <TASK>[ +0.000003] __flush_workqueue+0x203/0x840[ +0.000006] ? mutex_unlock+0x84/0xd0[ +0.000008] ? __pfx_mutex_unlock+0x10/0x10[ +0.000004] ? __pfx___flush_workqueue+0x10/0x10[ +0.000006] ? mutex_lock+0xa3/0xf0[ +0.000005] ib_cache_cleanup_one+0x39/0x190 [ib_core][ +0.000174] __ib_unregister_device+0x84/0xf0 [ib_core][ +0.000094] ib_unregister_device+0x25/0x30 [ib_core][ +0.000093] irdma_ib_unregister_device+0x97/0xc0 [irdma][ +0.000064] ? __pfx_irdma_ib_unregister_device+0x10/0x10 [irdma][ +0.000059] ? up_write+0x5c/0x90[ +0.000005] irdma_remove+0x36/0x90 [irdma][ +0.000062] auxiliary_bus_remove+0x32/0x50[ +0.000007] device_r---truncated--- 漏洞公开时间:2024-05-22 00:15:14 漏洞创建时间:2024-05-22 03:00:55 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2023-52743 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/1ad4112c9fcf0bc08222b2b1614fba52ffd12255 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/87a5e3fc8416106e290c448fc8a6dd50ab24c634 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ca834a017851c50464c25a85f3cb2daefff7bede | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/df59e05401450973c8c7e96fd74b49e24442dc1f | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52743 | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2023/CVE-2023-52743.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/stable/c/87a5e3fc8416106e290c448fc8a6dd50ab24c634 | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/stable/c/1ad4112c9fcf0bc08222b2b1614fba52ffd12255 | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/stable/c/ca834a017851c50464c25a85f3cb2daefff7bede | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/stable/c/df59e05401450973c8c7e96fd74b49e24442dc1f | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://git.kernel.org/stable/c/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2023-52743 | https://bugzilla.suse.com/show_bug.cgi?id=1225003 | | redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024052102-CVE-2023-52743-f027@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2282788 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2023-52743 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/linus/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 (6.2-rc8) | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/stable/c/87a5e3fc8416106e290c448fc8a6dd50ab24c634 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/stable/c/1ad4112c9fcf0bc08222b2b1614fba52ffd12255 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/stable/c/ca834a017851c50464c25a85f3cb2daefff7bede | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/stable/c/df59e05401450973c8c7e96fd74b49e24442dc1f | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://git.kernel.org/stable/c/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2023-52743 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2023-52743 | https://ubuntu.com/security/CVE-2023-52743 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2023-52743 | https://ubuntu.com/security/CVE-2023-52743 | | debian | | https://security-tracker.debian.org/tracker/CVE-2023-52743 | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | linux | | https://git.kernel.org/linus/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 | https://git.kernel.org/linus/940b61af02f497fcd911b9e2d75c6b8cf76b92fd | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:ice: Do not use WQ_MEM_RECLAIM flag for workqueueWhen both ice and the irdma driver are loaded, a warning incheck_flush_dependency is being triggered. This is due to ice driverworkqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma oneis not.According to kernel documentation, this flag should be set if theworkqueue will be involved in the kernel s memory reclamation flow.Since it is not, there is no need for the ice driver s WQ to have thisflag set so remove it.Example trace:[ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0[ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2632 check_flush_dependency+0x178/0x1a0[ +0.000011] Modules linked in: bonding tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc rfkill vfat fat intel_rapl_msr intel_rapl_common isst_if_common skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel rapl intel_cstate rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_core_mod ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_cm iw_cm iTCO_wdt iTCO_vendor_support ipmi_ssif irdma mei_me ib_uverbsib_core intel_uncore joydev pcspkr i2c_i801 acpi_ipmi mei lpc_ich i2c_smbus intel_pch_thermal ioatdma ipmi_si acpi_power_meteracpi_pad xfs libcrc32c sd_mod t10_pi crc64_rocksoft crc64 sg ahci ixgbe libahci ice i40e igb crc32c_intel mdio i2c_algo_bit libata dca wmi dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse[ +0.000161] [last unloaded: bonding][ +0.000006] CPU: 0 PID: 728 Comm: kworker/0:2 Tainted: G S 6.2.0-rc2_next-queue-13jan-00458-gc20aabd57164 #1[ +0.000006] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0010.010620200716 01/06/2020[ +0.000003] Workqueue: ice ice_service_task [ice][ +0.000127] RIP: 0010:check_flush_dependency+0x178/0x1a0[ +0.000005] Code: 89 8e 02 01 e8 49 3d 40 00 49 8b 55 18 48 8d 8d d0 00 00 00 48 8d b3 d0 00 00 00 4d 89 e0 48 c7 c7 e0 3b 089f e8 bb d3 07 01 <0f> 0b e9 be fe ff ff 80 3d 24 89 8e 02 00 0f 85 6b ff ff ff e9 06[ +0.000004] RSP: 0018:ffff88810a39f990 EFLAGS: 00010282[ +0.000005] RAX: 0000000000000000 RBX: ffff888141bc2400 RCX: 0000000000000000[ +0.000004] RDX: 0000000000000001 RSI: dffffc0000000000 RDI: ffffffffa1213a80[ +0.000003] RBP: ffff888194bf3400 R08: ffffed117b306112 R09: ffffed117b306112[ +0.000003] R10: ffff888bd983088b R11: ffffed117b306111 R12: 0000000000000000[ +0.000003] R13: ffff888111f84d00 R14: ffff88810a3943ac R15: ffff888194bf3400[ +0.000004] FS: 0000000000000000(0000) GS:ffff888bd9800000(0000) knlGS:0000000000000000[ +0.000003] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033[ +0.000003] CR2: 000056035b208b60 CR3: 000000017795e005 CR4: 00000000007706f0[ +0.000003] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000[ +0.000003] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400[ +0.000002] PKRU: 55555554[ +0.000003] Call Trace:[ +0.000002] <TASK>[ +0.000003] __flush_workqueue+0x203/0x840[ +0.000006] ? mutex_unlock+0x84/0xd0[ +0.000008] ? __pfx_mutex_unlock+0x10/0x10[ +0.000004] ? __pfx___flush_workqueue+0x10/0x10[ +0.000006] ? mutex_lock+0xa3/0xf0[ +0.000005] ib_cache_cleanup_one+0x39/0x190 [ib_core][ +0.000174] __ib_unregister_device+0x84/0xf0 [ib_core][ +0.000094] ib_unregister_device+0x25/0x30 [ib_core][ +0.000093] irdma_ib_unregister_device+0x97/0xc0 [irdma][ +0.000064] ? __pfx_irdma_ib_unregister_device+0x10/0x10 [irdma][ +0.000059] ? up_write+0x5c/0x90[ +0.000005] irdma_remove+0x36/0x90 [irdma][ +0.000062] auxiliary_bus_remove+0x32/0x50[ +0.000007] device_r---truncated--- openEuler评分: 4.0 Vector:CVSS:2.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L 受影响版本排查(受影响/不受影响): 1.openEuler-22.03-LTS-SP1(5.10.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.master(6.1.0):不受影响 6.openEuler-24.03-LTS(6.6.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-SP1(5.10.0):否 3.openEuler-22.03-LTS-SP3(5.10.0):否 4.master(6.1.0):否 5.openEuler-24.03-LTS(6.6.0):否 6.openEuler-24.03-LTS-Next(6.6.0):否 7.openEuler-22.03-LTS-SP4(5.10.0):否 三、漏洞修复 安全公告链接:https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-1860
评论 (
18
)
登录
后才可以发表评论
状态
已完成
待办的
已挂起
进行中
已完成
已拒绝
负责人
未设置
sanglipeng
sanglipeng
负责人
协作者
+负责人
+协作者
标签
CVE/UNAFFECTED
sig/Kernel
未设置
项目
未立项任务
未立项任务
Pull Requests
未关联
未关联
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
未关联
分支 (38)
标签 (265)
master
openEuler-24.03-LTS-SP2
openEuler-24.03-LTS-SP1
openEuler-24.03-LTS
openEuler-20.03-LTS-SP4
openEuler-22.03-LTS-SP4
openEuler-22.03-LTS-SP3
openEuler-24.03-LTS-SP3
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-20251017
openEuler-22.03-LTS-SP3-update-20251017
openEuler-24.03-LTS-update-20251017
openEuler-24.03-LTS-SP1-update-20251017
openEuler-24.03-LTS-SP2-update-20251017
openEuler-22.03-LTS-SP4-update-20251017
openEuler-20.03-LTS-SP4-update-20251011
openEuler-22.03-LTS-SP4-update-20251011
openEuler-22.03-LTS-SP3-update-20251011
openEuler-24.03-LTS-update-20250929
openEuler-25.09-release
openEuler-20.03-LTS-SP4-update-20250926
openEuler-24.03-LTS-update-20250926
openEuler-22.03-LTS-SP3-update-20250926
openEuler-22.03-LTS-SP4-update-20250926
openEuler-24.03-LTS-SP1-update-20250926
openEuler-24.03-LTS-SP2-update-20250926
openEuler-20.03-LTS-SP4-update-20250919
openEuler-22.03-LTS-SP3-update-20250919
openEuler-24.03-LTS-update-20250919
openEuler-22.03-LTS-SP4-update-20250919
openEuler-24.03-LTS-SP1-update-20250919
openEuler-24.03-LTS-SP2-update-20250919
openEuler-20.03-LTS-SP4-update-20250912
openEuler-22.03-LTS-SP3-update-20250912
openEuler-22.03-LTS-SP4-update-20250912
openEuler-24.03-LTS-update-20250912
openEuler-24.03-LTS-SP1-update-20250912
openEuler-24.03-LTS-SP2-update-20250912
openEuler-24.03-LTS-SP1-update-20250911
openEuler-24.03-LTS-update-20250905
openEuler-20.03-LTS-SP4-update-20250905
openEuler-22.03-LTS-SP3-update-20250905
openEuler-22.03-LTS-SP4-update-20250905
openEuler-24.03-LTS-SP1-update-20250905
openEuler-24.03-LTS-SP2-update-20250905
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 帐号,请先登录后再操作。
立即登录
没有帐号,去注册