Sign in
Sign up
Explore
Enterprise
Education
Search
Help
Terms of use
About Us
Explore
Enterprise
Education
Gitee Premium
Gitee AI
AI teammates
Sign in
Sign up
Fetch the repository succeeded.
description of repo status
Open Source
>
Other
>
Operation System
&&
Donate
Please sign in before you donate.
Cancel
Sign in
Scan WeChat QR to Pay
Cancel
Complete
Prompt
Switch to Alipay.
OK
Cancel
Watch
Unwatch
Watching
Releases Only
Ignoring
128
Star
72
Fork
331
src-openEuler
/
kernel
Closed
Code
Issues
1197
Pull Requests
35
Wiki
Insights
Pipelines
Service
JavaDoc
PHPDoc
Quality Analysis
Jenkins for Gitee
Tencent CloudBase
Tencent Cloud Serverless
悬镜安全
Aliyun SAE
Codeblitz
SBOM
DevLens
Don’t show this again
Update failed. Please try again later!
Remove this flag
Content Risk Flag
This task is identified by
as the content contains sensitive information such as code security bugs, privacy leaks, etc., so it is only accessible to contributors of this repository.
CVE-2023-53509
Done
#ID0RFW
CVE和安全问题
openeuler-ci-bot
owner
Opened this issue
2025-10-01 20:46
一、漏洞信息 漏洞编号:[CVE-2023-53509](https://nvd.nist.gov/vuln/detail/CVE-2023-53509) 漏洞归属组件:[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:qed: allow sleep in qed_mcp_trace_dump()By default, qed_mcp_cmd_and_union() delays 10us at a time in a loopthat can run 500K times, so calls to qed_mcp_nvm_rd_cmd()may block the current thread for over 5s.We observed thread scheduling delays over 700ms in production,with stacktraces pointing to this code as the culprit.qed_mcp_trace_dump() is called from ethtool, so sleeping is permitted.It already can sleep in qed_mcp_halt(), which calls qed_mcp_cmd().Add a can sleep parameter to qed_find_nvram_image() andqed_nvram_read() so they can sleep during qed_mcp_trace_dump().qed_mcp_trace_get_meta_info() and qed_mcp_trace_read_meta(),called only by qed_mcp_trace_dump(), allow these functions to sleep.I can t tell if the other caller (qed_grc_dump_mcp_hw_dump()) can sleep,so keep b_can_sleep set to false when it calls these functions.An example stacktrace from a custom warning we added to the kernelshowing a thread that has not scheduled despite long needing resched:[ 2745.362925,17] ------------[ cut here ]------------[ 2745.362941,17] WARNING: CPU: 23 PID: 5640 at arch/x86/kernel/irq.c:233 do_IRQ+0x15e/0x1a0()[ 2745.362946,17] Thread not rescheduled for 744 ms after irq 99[ 2745.362956,17] Modules linked in: ...[ 2745.363339,17] CPU: 23 PID: 5640 Comm: lldpd Tainted: P O 4.4.182+ #202104120910+6d1da174272d.61x[ 2745.363343,17] Hardware name: FOXCONN MercuryB/Quicksilver Controller, BIOS H11P1N09 07/08/2020[ 2745.363346,17] 0000000000000000 ffff885ec07c3ed8 ffffffff8131eb2f ffff885ec07c3f20[ 2745.363358,17] ffffffff81d14f64 ffff885ec07c3f10 ffffffff81072ac2 ffff88be98ed0000[ 2745.363369,17] 0000000000000063 0000000000000174 0000000000000074 0000000000000000[ 2745.363379,17] Call Trace:[ 2745.363382,17] <IRQ> [<ffffffff8131eb2f>] dump_stack+0x8e/0xcf[ 2745.363393,17] [<ffffffff81072ac2>] warn_slowpath_common+0x82/0xc0[ 2745.363398,17] [<ffffffff81072b4c>] warn_slowpath_fmt+0x4c/0x50[ 2745.363404,17] [<ffffffff810d5a8e>] ? rcu_irq_exit+0xae/0xc0[ 2745.363408,17] [<ffffffff817c99fe>] do_IRQ+0x15e/0x1a0[ 2745.363413,17] [<ffffffff817c7ac9>] common_interrupt+0x89/0x89[ 2745.363416,17] <EOI> [<ffffffff8132aa74>] ? delay_tsc+0x24/0x50[ 2745.363425,17] [<ffffffff8132aa04>] __udelay+0x34/0x40[ 2745.363457,17] [<ffffffffa04d45ff>] qed_mcp_cmd_and_union+0x36f/0x7d0 [qed][ 2745.363473,17] [<ffffffffa04d5ced>] qed_mcp_nvm_rd_cmd+0x4d/0x90 [qed][ 2745.363490,17] [<ffffffffa04e1dc7>] qed_mcp_trace_dump+0x4a7/0x630 [qed][ 2745.363504,17] [<ffffffffa04e2556>] ? qed_fw_asserts_dump+0x1d6/0x1f0 [qed][ 2745.363520,17] [<ffffffffa04e4ea7>] qed_dbg_mcp_trace_get_dump_buf_size+0x37/0x80 [qed][ 2745.363536,17] [<ffffffffa04ea881>] qed_dbg_feature_size+0x61/0xa0 [qed][ 2745.363551,17] [<ffffffffa04eb427>] qed_dbg_all_data_size+0x247/0x260 [qed][ 2745.363560,17] [<ffffffffa0482c10>] qede_get_regs_len+0x30/0x40 [qede][ 2745.363566,17] [<ffffffff816c9783>] ethtool_get_drvinfo+0xe3/0x190[ 2745.363570,17] [<ffffffff816cc152>] dev_ethtool+0x1362/0x2140[ 2745.363575,17] [<ffffffff8109bcc6>] ? finish_task_switch+0x76/0x260[ 2745.363580,17] [<ffffffff817c2116>] ? __schedule+0x3c6/0x9d0[ 2745.363585,17] [<ffffffff810dbd50>] ? hrtimer_start_range_ns+0x1d0/0x370[ 2745.363589,17] [<ffffffff816c1e5b>] ? dev_get_by_name_rcu+0x6b/0x90[ 2745.363594,17] [<ffffffff816de6a8>] dev_ioctl+0xe8/0x710[ 2745.363599,17] [<ffffffff816a58a8>] sock_do_ioctl+0x48/0x60[ 2745.363603,17] [<ffffffff816a5d87>] sock_ioctl+0x1c7/0x280[ 2745.363608,17] [<ffffffff8111f393>] ? seccomp_phase1+0x83/0x220[ 2745.363612,17] [<ffffffff811e3503>] do_vfs_ioctl+0x2b3/0x4e0[ 2745.363616,17] [<ffffffff811e3771>] SyS_ioctl+0x41/0x70[ 2745.363619,17] [<ffffffff817c6ffe>] entry_SYSCALL_64_fastpath+0x1e/0x79[ 2745.363622,17] ---[ end trace f6954aa440266421 ]--- 漏洞公开时间:2025-10-01 20:15:54 漏洞创建时间:2025-10-01 20:46:39 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2023-53509 <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/e0387f4f39a8d92302273ac356d1f6b2a38160d8 | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/50c81b35df01db12b348c5cbf4b1917dc9a7db54 | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/5401c3e0992860b11fb4b25796e4c4f1921740df | | ljqc | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:qed: allow sleep in qed_mcp_trace_dump()By default, qed_mcp_cmd_and_union() delays 10us at a time in a loopthat can run 500K times, so calls to qed_mcp_nvm_rd_cmd()may block the current thread for over 5s.We observed thread scheduling delays over 700ms in production,with stacktraces pointing to this code as the culprit.qed_mcp_trace_dump() is called from ethtool, so sleeping is permitted.It already can sleep in qed_mcp_halt(), which calls qed_mcp_cmd().Add a can sleep parameter to qed_find_nvram_image() andqed_nvram_read() so they can sleep during qed_mcp_trace_dump().qed_mcp_trace_get_meta_info() and qed_mcp_trace_read_meta(),called only by qed_mcp_trace_dump(), allow these functions to sleep.I can t tell if the other caller (qed_grc_dump_mcp_hw_dump()) can sleep,so keep b_can_sleep set to false when it calls these functions.An example stacktrace from a custom warning we added to the kernelshowing a thread that has not scheduled despite long needing resched:[ 2745.362925,17] ------------[ cut here ]------------[ 2745.362941,17] WARNING: CPU: 23 PID: 5640 at arch/x86/kernel/irq.c:233 do_IRQ+0x15e/0x1a0()[ 2745.362946,17] Thread not rescheduled for 744 ms after irq 99[ 2745.362956,17] Modules linked in: ...[ 2745.363339,17] CPU: 23 PID: 5640 Comm: lldpd Tainted: P O 4.4.182+ #202104120910+6d1da174272d.61x[ 2745.363343,17] Hardware name: FOXCONN MercuryB/Quicksilver Controller, BIOS H11P1N09 07/08/2020[ 2745.363346,17] 0000000000000000 ffff885ec07c3ed8 ffffffff8131eb2f ffff885ec07c3f20[ 2745.363358,17] ffffffff81d14f64 ffff885ec07c3f10 ffffffff81072ac2 ffff88be98ed0000[ 2745.363369,17] 0000000000000063 0000000000000174 0000000000000074 0000000000000000[ 2745.363379,17] Call Trace:[ 2745.363382,17] <IRQ> [<ffffffff8131eb2f>] dump_stack+0x8e/0xcf[ 2745.363393,17] [<ffffffff81072ac2>] warn_slowpath_common+0x82/0xc0[ 2745.363398,17] [<ffffffff81072b4c>] warn_slowpath_fmt+0x4c/0x50[ 2745.363404,17] [<ffffffff810d5a8e>] ? rcu_irq_exit+0xae/0xc0[ 2745.363408,17] [<ffffffff817c99fe>] do_IRQ+0x15e/0x1a0[ 2745.363413,17] [<ffffffff817c7ac9>] common_interrupt+0x89/0x89[ 2745.363416,17] <EOI> [<ffffffff8132aa74>] ? delay_tsc+0x24/0x50[ 2745.363425,17] [<ffffffff8132aa04>] __udelay+0x34/0x40[ 2745.363457,17] [<ffffffffa04d45ff>] qed_mcp_cmd_and_union+0x36f/0x7d0 [qed][ 2745.363473,17] [<ffffffffa04d5ced>] qed_mcp_nvm_rd_cmd+0x4d/0x90 [qed][ 2745.363490,17] [<ffffffffa04e1dc7>] qed_mcp_trace_dump+0x4a7/0x630 [qed][ 2745.363504,17] [<ffffffffa04e2556>] ? qed_fw_asserts_dump+0x1d6/0x1f0 [qed][ 2745.363520,17] [<ffffffffa04e4ea7>] qed_dbg_mcp_trace_get_dump_buf_size+0x37/0x80 [qed][ 2745.363536,17] [<ffffffffa04ea881>] qed_dbg_feature_size+0x61/0xa0 [qed][ 2745.363551,17] [<ffffffffa04eb427>] qed_dbg_all_data_size+0x247/0x260 [qed][ 2745.363560,17] [<ffffffffa0482c10>] qede_get_regs_len+0x30/0x40 [qede][ 2745.363566,17] [<ffffffff816c9783>] ethtool_get_drvinfo+0xe3/0x190[ 2745.363570,17] [<ffffffff816cc152>] dev_ethtool+0x1362/0x2140[ 2745.363575,17] [<ffffffff8109bcc6>] ? finish_task_switch+0x76/0x260[ 2745.363580,17] [<ffffffff817c2116>] ? __schedule+0x3c6/0x9d0[ 2745.363585,17] [<ffffffff810dbd50>] ? hrtimer_start_range_ns+0x1d0/0x370[ 2745.363589,17] [<ffffffff816c1e5b>] ? dev_get_by_name_rcu+0x6b/0x90[ 2745.363594,17] [<ffffffff816de6a8>] dev_ioctl+0xe8/0x710[ 2745.363599,17] [<ffffffff816a58a8>] sock_do_ioctl+0x48/0x60[ 2745.363603,17] [<ffffffff816a5d87>] sock_ioctl+0x1c7/0x280[ 2745.363608,17] [<ffffffff8111f393>] ? seccomp_phase1+0x83/0x220[ 2745.363612,17] [<ffffffff811e3503>] do_vfs_ioctl+0x2b3/0x4e0[ 2745.363616,17] [<ffffffff811e3771>] SyS_ioctl+0x41/0x70[ 2745.363619,17] [<ffffffff817c6ffe>] entry_SYSCALL_64_fastpath+0x1e/0x79[ 2745.363622,17] ---[ end trace f6954aa440266421 ]--- openEuler评分: 4.4 Vector:CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/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.master(6.12.33):不受影响 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.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.master(6.12.33):不受影响-漏洞代码不能被攻击者触发 5.openEuler-24.03-LTS:不受影响-漏洞代码不能被攻击者触发 6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发 7.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不能被攻击者触发 8.openEuler-24.03-LTS-SP2:不受影响-漏洞代码不能被攻击者触发
一、漏洞信息 漏洞编号:[CVE-2023-53509](https://nvd.nist.gov/vuln/detail/CVE-2023-53509) 漏洞归属组件:[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:qed: allow sleep in qed_mcp_trace_dump()By default, qed_mcp_cmd_and_union() delays 10us at a time in a loopthat can run 500K times, so calls to qed_mcp_nvm_rd_cmd()may block the current thread for over 5s.We observed thread scheduling delays over 700ms in production,with stacktraces pointing to this code as the culprit.qed_mcp_trace_dump() is called from ethtool, so sleeping is permitted.It already can sleep in qed_mcp_halt(), which calls qed_mcp_cmd().Add a can sleep parameter to qed_find_nvram_image() andqed_nvram_read() so they can sleep during qed_mcp_trace_dump().qed_mcp_trace_get_meta_info() and qed_mcp_trace_read_meta(),called only by qed_mcp_trace_dump(), allow these functions to sleep.I can t tell if the other caller (qed_grc_dump_mcp_hw_dump()) can sleep,so keep b_can_sleep set to false when it calls these functions.An example stacktrace from a custom warning we added to the kernelshowing a thread that has not scheduled despite long needing resched:[ 2745.362925,17] ------------[ cut here ]------------[ 2745.362941,17] WARNING: CPU: 23 PID: 5640 at arch/x86/kernel/irq.c:233 do_IRQ+0x15e/0x1a0()[ 2745.362946,17] Thread not rescheduled for 744 ms after irq 99[ 2745.362956,17] Modules linked in: ...[ 2745.363339,17] CPU: 23 PID: 5640 Comm: lldpd Tainted: P O 4.4.182+ #202104120910+6d1da174272d.61x[ 2745.363343,17] Hardware name: FOXCONN MercuryB/Quicksilver Controller, BIOS H11P1N09 07/08/2020[ 2745.363346,17] 0000000000000000 ffff885ec07c3ed8 ffffffff8131eb2f ffff885ec07c3f20[ 2745.363358,17] ffffffff81d14f64 ffff885ec07c3f10 ffffffff81072ac2 ffff88be98ed0000[ 2745.363369,17] 0000000000000063 0000000000000174 0000000000000074 0000000000000000[ 2745.363379,17] Call Trace:[ 2745.363382,17] <IRQ> [<ffffffff8131eb2f>] dump_stack+0x8e/0xcf[ 2745.363393,17] [<ffffffff81072ac2>] warn_slowpath_common+0x82/0xc0[ 2745.363398,17] [<ffffffff81072b4c>] warn_slowpath_fmt+0x4c/0x50[ 2745.363404,17] [<ffffffff810d5a8e>] ? rcu_irq_exit+0xae/0xc0[ 2745.363408,17] [<ffffffff817c99fe>] do_IRQ+0x15e/0x1a0[ 2745.363413,17] [<ffffffff817c7ac9>] common_interrupt+0x89/0x89[ 2745.363416,17] <EOI> [<ffffffff8132aa74>] ? delay_tsc+0x24/0x50[ 2745.363425,17] [<ffffffff8132aa04>] __udelay+0x34/0x40[ 2745.363457,17] [<ffffffffa04d45ff>] qed_mcp_cmd_and_union+0x36f/0x7d0 [qed][ 2745.363473,17] [<ffffffffa04d5ced>] qed_mcp_nvm_rd_cmd+0x4d/0x90 [qed][ 2745.363490,17] [<ffffffffa04e1dc7>] qed_mcp_trace_dump+0x4a7/0x630 [qed][ 2745.363504,17] [<ffffffffa04e2556>] ? qed_fw_asserts_dump+0x1d6/0x1f0 [qed][ 2745.363520,17] [<ffffffffa04e4ea7>] qed_dbg_mcp_trace_get_dump_buf_size+0x37/0x80 [qed][ 2745.363536,17] [<ffffffffa04ea881>] qed_dbg_feature_size+0x61/0xa0 [qed][ 2745.363551,17] [<ffffffffa04eb427>] qed_dbg_all_data_size+0x247/0x260 [qed][ 2745.363560,17] [<ffffffffa0482c10>] qede_get_regs_len+0x30/0x40 [qede][ 2745.363566,17] [<ffffffff816c9783>] ethtool_get_drvinfo+0xe3/0x190[ 2745.363570,17] [<ffffffff816cc152>] dev_ethtool+0x1362/0x2140[ 2745.363575,17] [<ffffffff8109bcc6>] ? finish_task_switch+0x76/0x260[ 2745.363580,17] [<ffffffff817c2116>] ? __schedule+0x3c6/0x9d0[ 2745.363585,17] [<ffffffff810dbd50>] ? hrtimer_start_range_ns+0x1d0/0x370[ 2745.363589,17] [<ffffffff816c1e5b>] ? dev_get_by_name_rcu+0x6b/0x90[ 2745.363594,17] [<ffffffff816de6a8>] dev_ioctl+0xe8/0x710[ 2745.363599,17] [<ffffffff816a58a8>] sock_do_ioctl+0x48/0x60[ 2745.363603,17] [<ffffffff816a5d87>] sock_ioctl+0x1c7/0x280[ 2745.363608,17] [<ffffffff8111f393>] ? seccomp_phase1+0x83/0x220[ 2745.363612,17] [<ffffffff811e3503>] do_vfs_ioctl+0x2b3/0x4e0[ 2745.363616,17] [<ffffffff811e3771>] SyS_ioctl+0x41/0x70[ 2745.363619,17] [<ffffffff817c6ffe>] entry_SYSCALL_64_fastpath+0x1e/0x79[ 2745.363622,17] ---[ end trace f6954aa440266421 ]--- 漏洞公开时间:2025-10-01 20:15:54 漏洞创建时间:2025-10-01 20:46:39 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2023-53509 <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/e0387f4f39a8d92302273ac356d1f6b2a38160d8 | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/50c81b35df01db12b348c5cbf4b1917dc9a7db54 | | ljqc | | gregkh/linux | | https://git.kernel.org/stable/c/5401c3e0992860b11fb4b25796e4c4f1921740df | | ljqc | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:qed: allow sleep in qed_mcp_trace_dump()By default, qed_mcp_cmd_and_union() delays 10us at a time in a loopthat can run 500K times, so calls to qed_mcp_nvm_rd_cmd()may block the current thread for over 5s.We observed thread scheduling delays over 700ms in production,with stacktraces pointing to this code as the culprit.qed_mcp_trace_dump() is called from ethtool, so sleeping is permitted.It already can sleep in qed_mcp_halt(), which calls qed_mcp_cmd().Add a can sleep parameter to qed_find_nvram_image() andqed_nvram_read() so they can sleep during qed_mcp_trace_dump().qed_mcp_trace_get_meta_info() and qed_mcp_trace_read_meta(),called only by qed_mcp_trace_dump(), allow these functions to sleep.I can t tell if the other caller (qed_grc_dump_mcp_hw_dump()) can sleep,so keep b_can_sleep set to false when it calls these functions.An example stacktrace from a custom warning we added to the kernelshowing a thread that has not scheduled despite long needing resched:[ 2745.362925,17] ------------[ cut here ]------------[ 2745.362941,17] WARNING: CPU: 23 PID: 5640 at arch/x86/kernel/irq.c:233 do_IRQ+0x15e/0x1a0()[ 2745.362946,17] Thread not rescheduled for 744 ms after irq 99[ 2745.362956,17] Modules linked in: ...[ 2745.363339,17] CPU: 23 PID: 5640 Comm: lldpd Tainted: P O 4.4.182+ #202104120910+6d1da174272d.61x[ 2745.363343,17] Hardware name: FOXCONN MercuryB/Quicksilver Controller, BIOS H11P1N09 07/08/2020[ 2745.363346,17] 0000000000000000 ffff885ec07c3ed8 ffffffff8131eb2f ffff885ec07c3f20[ 2745.363358,17] ffffffff81d14f64 ffff885ec07c3f10 ffffffff81072ac2 ffff88be98ed0000[ 2745.363369,17] 0000000000000063 0000000000000174 0000000000000074 0000000000000000[ 2745.363379,17] Call Trace:[ 2745.363382,17] <IRQ> [<ffffffff8131eb2f>] dump_stack+0x8e/0xcf[ 2745.363393,17] [<ffffffff81072ac2>] warn_slowpath_common+0x82/0xc0[ 2745.363398,17] [<ffffffff81072b4c>] warn_slowpath_fmt+0x4c/0x50[ 2745.363404,17] [<ffffffff810d5a8e>] ? rcu_irq_exit+0xae/0xc0[ 2745.363408,17] [<ffffffff817c99fe>] do_IRQ+0x15e/0x1a0[ 2745.363413,17] [<ffffffff817c7ac9>] common_interrupt+0x89/0x89[ 2745.363416,17] <EOI> [<ffffffff8132aa74>] ? delay_tsc+0x24/0x50[ 2745.363425,17] [<ffffffff8132aa04>] __udelay+0x34/0x40[ 2745.363457,17] [<ffffffffa04d45ff>] qed_mcp_cmd_and_union+0x36f/0x7d0 [qed][ 2745.363473,17] [<ffffffffa04d5ced>] qed_mcp_nvm_rd_cmd+0x4d/0x90 [qed][ 2745.363490,17] [<ffffffffa04e1dc7>] qed_mcp_trace_dump+0x4a7/0x630 [qed][ 2745.363504,17] [<ffffffffa04e2556>] ? qed_fw_asserts_dump+0x1d6/0x1f0 [qed][ 2745.363520,17] [<ffffffffa04e4ea7>] qed_dbg_mcp_trace_get_dump_buf_size+0x37/0x80 [qed][ 2745.363536,17] [<ffffffffa04ea881>] qed_dbg_feature_size+0x61/0xa0 [qed][ 2745.363551,17] [<ffffffffa04eb427>] qed_dbg_all_data_size+0x247/0x260 [qed][ 2745.363560,17] [<ffffffffa0482c10>] qede_get_regs_len+0x30/0x40 [qede][ 2745.363566,17] [<ffffffff816c9783>] ethtool_get_drvinfo+0xe3/0x190[ 2745.363570,17] [<ffffffff816cc152>] dev_ethtool+0x1362/0x2140[ 2745.363575,17] [<ffffffff8109bcc6>] ? finish_task_switch+0x76/0x260[ 2745.363580,17] [<ffffffff817c2116>] ? __schedule+0x3c6/0x9d0[ 2745.363585,17] [<ffffffff810dbd50>] ? hrtimer_start_range_ns+0x1d0/0x370[ 2745.363589,17] [<ffffffff816c1e5b>] ? dev_get_by_name_rcu+0x6b/0x90[ 2745.363594,17] [<ffffffff816de6a8>] dev_ioctl+0xe8/0x710[ 2745.363599,17] [<ffffffff816a58a8>] sock_do_ioctl+0x48/0x60[ 2745.363603,17] [<ffffffff816a5d87>] sock_ioctl+0x1c7/0x280[ 2745.363608,17] [<ffffffff8111f393>] ? seccomp_phase1+0x83/0x220[ 2745.363612,17] [<ffffffff811e3503>] do_vfs_ioctl+0x2b3/0x4e0[ 2745.363616,17] [<ffffffff811e3771>] SyS_ioctl+0x41/0x70[ 2745.363619,17] [<ffffffff817c6ffe>] entry_SYSCALL_64_fastpath+0x1e/0x79[ 2745.363622,17] ---[ end trace f6954aa440266421 ]--- openEuler评分: 4.4 Vector:CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/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.master(6.12.33):不受影响 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.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.master(6.12.33):不受影响-漏洞代码不能被攻击者触发 5.openEuler-24.03-LTS:不受影响-漏洞代码不能被攻击者触发 6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发 7.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不能被攻击者触发 8.openEuler-24.03-LTS-SP2:不受影响-漏洞代码不能被攻击者触发
Comments (
5
)
Sign in
to comment
Status
Done
Backlog
已挂起
Doing
Done
Declined
Assignees
Not set
CTC-Xibo.Wang
CTC-XiboWang
Assignee
Collaborator
+Assign
+Mention
Labels
CVE/FIXED
sig/Kernel
Not set
Projects
Unprojected
Unprojected
Milestones
No related milestones
No related milestones
Pull Requests
None yet
None yet
Successfully merging a pull request will close this issue.
Branches
No related branch
Branches (
-
)
Tags (
-
)
Planed to start   -   Planed to end
-
Top level
Not Top
Top Level: High
Top Level: Medium
Top Level: Low
Priority
Not specified
Serious
Main
Secondary
Unimportant
Duration
(hours)
参与者(2)
1
https://gitee.com/src-openeuler/kernel.git
git@gitee.com:src-openeuler/kernel.git
src-openeuler
kernel
kernel
Going to Help Center
Search
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
Comment
Repository Report
Back to the top
Login prompt
This operation requires login to the code cloud account. Please log in before operating.
Go to login
No account. Register