登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
模力方舟
AI 队友
登录
注册
轻量养虾,开箱即用!低 Token + 稳定算力,Gitee & 模力方舟联合出品的 PocketClaw 正式开售!点击了解详情
代码拉取完成,页面将自动刷新
仓库状态说明
开源项目
>
其他开源
>
操作系统
&&
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
128
Star
73
Fork
329
src-openEuler
/
kernel
关闭
代码
Issues
1197
Pull Requests
35
Wiki
统计
流水线
服务
JavaDoc
PHPDoc
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
SBOM
我知道了,不再自动展开
更新失败,请稍后重试!
移除标识
内容风险标识
本任务被
标识为内容中包含有代码安全 Bug 、隐私泄露等敏感信息,仓库外成员不可访问
CVE-2023-53455
已完成
#ID0RE8
CVE和安全问题
openeuler-ci-bot
拥有者
创建于
2025-10-01 20:33
一、漏洞信息 漏洞编号:[CVE-2023-53455](https://nvd.nist.gov/vuln/detail/CVE-2023-53455) 漏洞归属组件:[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/ 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:drm/vc4: drop all currently held locks if deadlock happensIf vc4_hdmi_reset_link() returns -EDEADLK, it means that a deadlockhappened in the locking context. This situation should be addressed bydropping all currently held locks and block until the contended lockbecomes available. Currently, vc4 is not dealing with the deadlockproperly, producing the following output when PROVE_LOCKING is enabled:[ 825.612809] ------------[ cut here ]------------[ 825.612852] WARNING: CPU: 1 PID: 116 at drivers/gpu/drm/drm_modeset_lock.c:276 drm_modeset_drop_locks+0x60/0x68 [drm][ 825.613458] Modules linked in: 8021q mrp garp stp llcraspberrypi_cpufreq brcmfmac brcmutil crct10dif_ce hci_uart cfg80211btqca btbcm bluetooth vc4 raspberrypi_hwmon snd_soc_hdmi_codec cecclk_raspberrypi ecdh_generic drm_display_helper ecc rfkilldrm_dma_helper drm_kms_helper pwm_bcm2835 bcm2835_thermal bcm2835_rngrng_core i2c_bcm2835 drm fuse ip_tables x_tables ipv6[ 825.613735] CPU: 1 PID: 116 Comm: kworker/1:2 Tainted: G W 6.1.0-rc6-01399-g941aae326315 #3[ 825.613759] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT)[ 825.613777] Workqueue: events output_poll_execute [drm_kms_helper][ 825.614038] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)[ 825.614063] pc : drm_modeset_drop_locks+0x60/0x68 [drm][ 825.614603] lr : drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper][ 825.614829] sp : ffff800008313bf0[ 825.614844] x29: ffff800008313bf0 x28: ffffcd7778b8b000 x27: 0000000000000000[ 825.614883] x26: 0000000000000001 x25: 0000000000000001 x24: ffff677cc35c2758[ 825.614920] x23: ffffcd7707d01430 x22: ffffcd7707c3edc7 x21: 0000000000000001[ 825.614958] x20: 0000000000000000 x19: ffff800008313c10 x18: 000000000000b6d3[ 825.614995] x17: ffffcd777835e214 x16: ffffcd7777cef870 x15: fffff81000000000[ 825.615033] x14: 0000000000000000 x13: 0000000000000099 x12: 0000000000000002[ 825.615070] x11: 72917988020af800 x10: 72917988020af800 x9 : 72917988020af800[ 825.615108] x8 : ffff677cc665e0a8 x7 : d00a8c180000110c x6 : ffffcd77774c0054[ 825.615145] x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000[ 825.615181] x2 : ffff677cc55e1880 x1 : ffffcd7777cef8ec x0 : ffff800008313c10[ 825.615219] Call trace:[ 825.615232] drm_modeset_drop_locks+0x60/0x68 [drm][ 825.615773] drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper][ 825.616003] output_poll_execute+0xe4/0x224 [drm_kms_helper][ 825.616233] process_one_work+0x2b4/0x618[ 825.616264] worker_thread+0x24c/0x464[ 825.616288] kthread+0xec/0x110[ 825.616310] ret_from_fork+0x10/0x20[ 825.616335] irq event stamp: 7634[ 825.616349] hardirqs last enabled at (7633): [<ffffcd777831ee90>] _raw_spin_unlock_irq+0x3c/0x78[ 825.616384] hardirqs last disabled at (7634): [<ffffcd7778315a78>] __schedule+0x134/0x9f0[ 825.616411] softirqs last enabled at (7630): [<ffffcd7707aacea0>] local_bh_enable+0x4/0x30 [ipv6][ 825.617019] softirqs last disabled at (7618): [<ffffcd7707aace70>] local_bh_disable+0x4/0x30 [ipv6][ 825.617586] ---[ end trace 0000000000000000 ]---Therefore, deal with the deadlock as suggested by [1], using thefunction drm_modeset_backoff().[1] https://docs.kernel.org/gpu/drm-kms.html?highlight=kms#kms-locking 漏洞公开时间:2025-10-01 20:15:44 漏洞创建时间:2025-10-01 20:33:26 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2023-53455 <details> <summary>更多参考(点击展开)</summary> 无 </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: 七彩瞬析开源风险感知平台 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | gregkh/linux | | https://git.kernel.org/stable/c/41286a53e7f54202fd277cd516724de3ab7497c7 | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/f483eda89a2e717daa7b15c8ca228a209f65617b | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/479d4f0be4237ba33bc9432787aeb62c90e30f95 | | ljqc | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:drm/vc4: drop all currently held locks if deadlock happensIf vc4_hdmi_reset_link() returns -EDEADLK, it means that a deadlockhappened in the locking context. This situation should be addressed bydropping all currently held locks and block until the contended lockbecomes available. Currently, vc4 is not dealing with the deadlockproperly, producing the following output when PROVE_LOCKING is enabled:[ 825.612809] ------------[ cut here ]------------[ 825.612852] WARNING: CPU: 1 PID: 116 at drivers/gpu/drm/drm_modeset_lock.c:276 drm_modeset_drop_locks+0x60/0x68 [drm][ 825.613458] Modules linked in: 8021q mrp garp stp llcraspberrypi_cpufreq brcmfmac brcmutil crct10dif_ce hci_uart cfg80211btqca btbcm bluetooth vc4 raspberrypi_hwmon snd_soc_hdmi_codec cecclk_raspberrypi ecdh_generic drm_display_helper ecc rfkilldrm_dma_helper drm_kms_helper pwm_bcm2835 bcm2835_thermal bcm2835_rngrng_core i2c_bcm2835 drm fuse ip_tables x_tables ipv6[ 825.613735] CPU: 1 PID: 116 Comm: kworker/1:2 Tainted: G W 6.1.0-rc6-01399-g941aae326315 #3[ 825.613759] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT)[ 825.613777] Workqueue: events output_poll_execute [drm_kms_helper][ 825.614038] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)[ 825.614063] pc : drm_modeset_drop_locks+0x60/0x68 [drm][ 825.614603] lr : drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper][ 825.614829] sp : ffff800008313bf0[ 825.614844] x29: ffff800008313bf0 x28: ffffcd7778b8b000 x27: 0000000000000000[ 825.614883] x26: 0000000000000001 x25: 0000000000000001 x24: ffff677cc35c2758[ 825.614920] x23: ffffcd7707d01430 x22: ffffcd7707c3edc7 x21: 0000000000000001[ 825.614958] x20: 0000000000000000 x19: ffff800008313c10 x18: 000000000000b6d3[ 825.614995] x17: ffffcd777835e214 x16: ffffcd7777cef870 x15: fffff81000000000[ 825.615033] x14: 0000000000000000 x13: 0000000000000099 x12: 0000000000000002[ 825.615070] x11: 72917988020af800 x10: 72917988020af800 x9 : 72917988020af800[ 825.615108] x8 : ffff677cc665e0a8 x7 : d00a8c180000110c x6 : ffffcd77774c0054[ 825.615145] x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000[ 825.615181] x2 : ffff677cc55e1880 x1 : ffffcd7777cef8ec x0 : ffff800008313c10[ 825.615219] Call trace:[ 825.615232] drm_modeset_drop_locks+0x60/0x68 [drm][ 825.615773] drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper][ 825.616003] output_poll_execute+0xe4/0x224 [drm_kms_helper][ 825.616233] process_one_work+0x2b4/0x618[ 825.616264] worker_thread+0x24c/0x464[ 825.616288] kthread+0xec/0x110[ 825.616310] ret_from_fork+0x10/0x20[ 825.616335] irq event stamp: 7634[ 825.616349] hardirqs last enabled at (7633): [<ffffcd777831ee90>] _raw_spin_unlock_irq+0x3c/0x78[ 825.616384] hardirqs last disabled at (7634): [<ffffcd7778315a78>] __schedule+0x134/0x9f0[ 825.616411] softirqs last enabled at (7630): [<ffffcd7707aacea0>] local_bh_enable+0x4/0x30 [ipv6][ 825.617019] softirqs last disabled at (7618): [<ffffcd7707aace70>] local_bh_disable+0x4/0x30 [ipv6][ 825.617586] ---[ end trace 0000000000000000 ]---Therefore, deal with the deadlock as suggested by [1], using thefunction drm_modeset_backoff().[1] <ahref= https://docs.kernel.org/gpu/drm-kms.html?highlight=kms#kms-locking >https://docs.kernel.org/gpu/drm-kms.html?highlight=kms#kms-locking</a>The Linux kernel CVE team has assigned CVE-2023-53455 to this issue. openEuler评分: 5.5 Vector:CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H 受影响版本排查(受影响/不受影响): 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.openEuler-24.03-LTS-Next:不受影响 7.openEuler-24.03-LTS-SP1:不受影响 8.openEuler-24.03-LTS-SP2:不受影响 修复是否涉及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.openEuler-24.03-LTS-Next:否 7.openEuler-24.03-LTS-SP1:否 8.openEuler-24.03-LTS-SP2:否 原因说明: 1.master(6.12.33):不受影响-漏洞代码不能被攻击者触发 2.openEuler-24.03-LTS:不受影响-漏洞代码不能被攻击者触发 3.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发 4.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不能被攻击者触发 5.openEuler-24.03-LTS-SP2:不受影响-漏洞代码不能被攻击者触发 6.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在 7.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在 8.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在
一、漏洞信息 漏洞编号:[CVE-2023-53455](https://nvd.nist.gov/vuln/detail/CVE-2023-53455) 漏洞归属组件:[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/ 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:drm/vc4: drop all currently held locks if deadlock happensIf vc4_hdmi_reset_link() returns -EDEADLK, it means that a deadlockhappened in the locking context. This situation should be addressed bydropping all currently held locks and block until the contended lockbecomes available. Currently, vc4 is not dealing with the deadlockproperly, producing the following output when PROVE_LOCKING is enabled:[ 825.612809] ------------[ cut here ]------------[ 825.612852] WARNING: CPU: 1 PID: 116 at drivers/gpu/drm/drm_modeset_lock.c:276 drm_modeset_drop_locks+0x60/0x68 [drm][ 825.613458] Modules linked in: 8021q mrp garp stp llcraspberrypi_cpufreq brcmfmac brcmutil crct10dif_ce hci_uart cfg80211btqca btbcm bluetooth vc4 raspberrypi_hwmon snd_soc_hdmi_codec cecclk_raspberrypi ecdh_generic drm_display_helper ecc rfkilldrm_dma_helper drm_kms_helper pwm_bcm2835 bcm2835_thermal bcm2835_rngrng_core i2c_bcm2835 drm fuse ip_tables x_tables ipv6[ 825.613735] CPU: 1 PID: 116 Comm: kworker/1:2 Tainted: G W 6.1.0-rc6-01399-g941aae326315 #3[ 825.613759] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT)[ 825.613777] Workqueue: events output_poll_execute [drm_kms_helper][ 825.614038] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)[ 825.614063] pc : drm_modeset_drop_locks+0x60/0x68 [drm][ 825.614603] lr : drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper][ 825.614829] sp : ffff800008313bf0[ 825.614844] x29: ffff800008313bf0 x28: ffffcd7778b8b000 x27: 0000000000000000[ 825.614883] x26: 0000000000000001 x25: 0000000000000001 x24: ffff677cc35c2758[ 825.614920] x23: ffffcd7707d01430 x22: ffffcd7707c3edc7 x21: 0000000000000001[ 825.614958] x20: 0000000000000000 x19: ffff800008313c10 x18: 000000000000b6d3[ 825.614995] x17: ffffcd777835e214 x16: ffffcd7777cef870 x15: fffff81000000000[ 825.615033] x14: 0000000000000000 x13: 0000000000000099 x12: 0000000000000002[ 825.615070] x11: 72917988020af800 x10: 72917988020af800 x9 : 72917988020af800[ 825.615108] x8 : ffff677cc665e0a8 x7 : d00a8c180000110c x6 : ffffcd77774c0054[ 825.615145] x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000[ 825.615181] x2 : ffff677cc55e1880 x1 : ffffcd7777cef8ec x0 : ffff800008313c10[ 825.615219] Call trace:[ 825.615232] drm_modeset_drop_locks+0x60/0x68 [drm][ 825.615773] drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper][ 825.616003] output_poll_execute+0xe4/0x224 [drm_kms_helper][ 825.616233] process_one_work+0x2b4/0x618[ 825.616264] worker_thread+0x24c/0x464[ 825.616288] kthread+0xec/0x110[ 825.616310] ret_from_fork+0x10/0x20[ 825.616335] irq event stamp: 7634[ 825.616349] hardirqs last enabled at (7633): [<ffffcd777831ee90>] _raw_spin_unlock_irq+0x3c/0x78[ 825.616384] hardirqs last disabled at (7634): [<ffffcd7778315a78>] __schedule+0x134/0x9f0[ 825.616411] softirqs last enabled at (7630): [<ffffcd7707aacea0>] local_bh_enable+0x4/0x30 [ipv6][ 825.617019] softirqs last disabled at (7618): [<ffffcd7707aace70>] local_bh_disable+0x4/0x30 [ipv6][ 825.617586] ---[ end trace 0000000000000000 ]---Therefore, deal with the deadlock as suggested by [1], using thefunction drm_modeset_backoff().[1] https://docs.kernel.org/gpu/drm-kms.html?highlight=kms#kms-locking 漏洞公开时间:2025-10-01 20:15:44 漏洞创建时间:2025-10-01 20:33:26 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2023-53455 <details> <summary>更多参考(点击展开)</summary> 无 </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: 七彩瞬析开源风险感知平台 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | gregkh/linux | | https://git.kernel.org/stable/c/41286a53e7f54202fd277cd516724de3ab7497c7 | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/f483eda89a2e717daa7b15c8ca228a209f65617b | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/479d4f0be4237ba33bc9432787aeb62c90e30f95 | | ljqc | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:drm/vc4: drop all currently held locks if deadlock happensIf vc4_hdmi_reset_link() returns -EDEADLK, it means that a deadlockhappened in the locking context. This situation should be addressed bydropping all currently held locks and block until the contended lockbecomes available. Currently, vc4 is not dealing with the deadlockproperly, producing the following output when PROVE_LOCKING is enabled:[ 825.612809] ------------[ cut here ]------------[ 825.612852] WARNING: CPU: 1 PID: 116 at drivers/gpu/drm/drm_modeset_lock.c:276 drm_modeset_drop_locks+0x60/0x68 [drm][ 825.613458] Modules linked in: 8021q mrp garp stp llcraspberrypi_cpufreq brcmfmac brcmutil crct10dif_ce hci_uart cfg80211btqca btbcm bluetooth vc4 raspberrypi_hwmon snd_soc_hdmi_codec cecclk_raspberrypi ecdh_generic drm_display_helper ecc rfkilldrm_dma_helper drm_kms_helper pwm_bcm2835 bcm2835_thermal bcm2835_rngrng_core i2c_bcm2835 drm fuse ip_tables x_tables ipv6[ 825.613735] CPU: 1 PID: 116 Comm: kworker/1:2 Tainted: G W 6.1.0-rc6-01399-g941aae326315 #3[ 825.613759] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT)[ 825.613777] Workqueue: events output_poll_execute [drm_kms_helper][ 825.614038] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)[ 825.614063] pc : drm_modeset_drop_locks+0x60/0x68 [drm][ 825.614603] lr : drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper][ 825.614829] sp : ffff800008313bf0[ 825.614844] x29: ffff800008313bf0 x28: ffffcd7778b8b000 x27: 0000000000000000[ 825.614883] x26: 0000000000000001 x25: 0000000000000001 x24: ffff677cc35c2758[ 825.614920] x23: ffffcd7707d01430 x22: ffffcd7707c3edc7 x21: 0000000000000001[ 825.614958] x20: 0000000000000000 x19: ffff800008313c10 x18: 000000000000b6d3[ 825.614995] x17: ffffcd777835e214 x16: ffffcd7777cef870 x15: fffff81000000000[ 825.615033] x14: 0000000000000000 x13: 0000000000000099 x12: 0000000000000002[ 825.615070] x11: 72917988020af800 x10: 72917988020af800 x9 : 72917988020af800[ 825.615108] x8 : ffff677cc665e0a8 x7 : d00a8c180000110c x6 : ffffcd77774c0054[ 825.615145] x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000[ 825.615181] x2 : ffff677cc55e1880 x1 : ffffcd7777cef8ec x0 : ffff800008313c10[ 825.615219] Call trace:[ 825.615232] drm_modeset_drop_locks+0x60/0x68 [drm][ 825.615773] drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper][ 825.616003] output_poll_execute+0xe4/0x224 [drm_kms_helper][ 825.616233] process_one_work+0x2b4/0x618[ 825.616264] worker_thread+0x24c/0x464[ 825.616288] kthread+0xec/0x110[ 825.616310] ret_from_fork+0x10/0x20[ 825.616335] irq event stamp: 7634[ 825.616349] hardirqs last enabled at (7633): [<ffffcd777831ee90>] _raw_spin_unlock_irq+0x3c/0x78[ 825.616384] hardirqs last disabled at (7634): [<ffffcd7778315a78>] __schedule+0x134/0x9f0[ 825.616411] softirqs last enabled at (7630): [<ffffcd7707aacea0>] local_bh_enable+0x4/0x30 [ipv6][ 825.617019] softirqs last disabled at (7618): [<ffffcd7707aace70>] local_bh_disable+0x4/0x30 [ipv6][ 825.617586] ---[ end trace 0000000000000000 ]---Therefore, deal with the deadlock as suggested by [1], using thefunction drm_modeset_backoff().[1] <ahref= https://docs.kernel.org/gpu/drm-kms.html?highlight=kms#kms-locking >https://docs.kernel.org/gpu/drm-kms.html?highlight=kms#kms-locking</a>The Linux kernel CVE team has assigned CVE-2023-53455 to this issue. openEuler评分: 5.5 Vector:CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H 受影响版本排查(受影响/不受影响): 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.openEuler-24.03-LTS-Next:不受影响 7.openEuler-24.03-LTS-SP1:不受影响 8.openEuler-24.03-LTS-SP2:不受影响 修复是否涉及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.openEuler-24.03-LTS-Next:否 7.openEuler-24.03-LTS-SP1:否 8.openEuler-24.03-LTS-SP2:否 原因说明: 1.master(6.12.33):不受影响-漏洞代码不能被攻击者触发 2.openEuler-24.03-LTS:不受影响-漏洞代码不能被攻击者触发 3.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发 4.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不能被攻击者触发 5.openEuler-24.03-LTS-SP2:不受影响-漏洞代码不能被攻击者触发 6.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在 7.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在 8.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在
评论 (
5
)
登录
后才可以发表评论
状态
已完成
待办的
已挂起
进行中
已完成
已拒绝
负责人
未设置
CTC-Xibo.Wang
CTC-XiboWang
负责人
协作者
+负责人
+协作者
标签
CVE/UNAFFECTED
sig/Kernel
未设置
项目
未立项任务
未立项任务
里程碑
未关联里程碑
未关联里程碑
Pull Requests
未关联
未关联
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
未关联
分支 (
-
)
标签 (
-
)
开始日期   -   截止日期
-
置顶选项
不置顶
置顶等级:高
置顶等级:中
置顶等级:低
优先级
不指定
严重
主要
次要
不重要
预计工期
(小时)
参与者(2)
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 帐号,请先登录后再操作。
立即登录
没有帐号,去注册