一、漏洞信息
漏洞编号:CVE-2021-47468
漏洞归属组件: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 V3.0分值:
BaseScore:0.0 None
Vector:CVSS:3.0/
漏洞简述:
In the Linux kernel, the following vulnerability has been resolved:isdn: mISDN: Fix sleeping function called from invalid contextThe driver can call card->isac.release() function from an atomiccontext.Fix this by calling this function after releasing the lock.The following log reveals it:[ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018[ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe[ 44.169574 ] INFO: lockdep is turned off.[ 44.169899 ] irq event stamp: 0[ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0[ 44.170627 ] hardirqs last disabled at (0): [] copy_process+0x132d/0x3e00[ 44.171240 ] softirqs last enabled at (0): [] copy_process+0x135a/0x3e00[ 44.171852 ] softirqs last disabled at (0): [<0000000000000000>] 0x0[ 44.172318 ] Preemption disabled at:[ 44.172320 ] [] nj_release+0x69/0x500 [netjet][ 44.174441 ] Call Trace:[ 44.174630 ] dump_stack_lvl+0xa8/0xd1[ 44.174912 ] dump_stack+0x15/0x17[ 44.175166 ] ___might_sleep+0x3a2/0x510[ 44.175459 ] ? nj_release+0x69/0x500 [netjet][ 44.175791 ] __might_sleep+0x82/0xe0[ 44.176063 ] ? start_flush_work+0x20/0x7b0[ 44.176375 ] start_flush_work+0x33/0x7b0[ 44.176672 ] ? trace_irq_enable_rcuidle+0x85/0x170[ 44.177034 ] ? kasan_quarantine_put+0xaa/0x1f0[ 44.177372 ] ? kasan_quarantine_put+0xaa/0x1f0[ 44.177711 ] __flush_work+0x11a/0x1a0[ 44.177991 ] ? flush_work+0x20/0x20[ 44.178257 ] ? lock_release+0x13c/0x8f0[ 44.178550 ] ? __kasan_check_write+0x14/0x20[ 44.178872 ] ? do_raw_spin_lock+0x148/0x360[ 44.179187 ] ? read_lock_is_recursive+0x20/0x20[ 44.179530 ] ? __kasan_check_read+0x11/0x20[ 44.179846 ] ? do_raw_spin_unlock+0x55/0x900[ 44.180168 ] ? ____kasan_slab_free+0x116/0x140[ 44.180505 ] ? _raw_spin_unlock_irqrestore+0x41/0x60[ 44.180878 ] ? skb_queue_purge+0x1a3/0x1c0[ 44.181189 ] ? kfree+0x13e/0x290[ 44.181438 ] flush_work+0x17/0x20[ 44.181695 ] mISDN_freedchannel+0xe8/0x100[ 44.182006 ] isac_release+0x210/0x260 [mISDNipac][ 44.182366 ] nj_release+0xf6/0x500 [netjet][ 44.182685 ] nj_remove+0x48/0x70 [netjet][ 44.182989 ] pci_device_remove+0xa9/0x250
漏洞公开时间:2024-05-22 15:15:11
漏洞创建时间:2024-05-22 08:31:45
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2021-47468
漏洞分析指导链接:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息:
影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 |
---|---|---|---|---|
linux | https://git.kernel.org/linus/6510e80a0b81b5d814e3aea6297ba42f5e76f73c | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
二、漏洞分析结构反馈
影响性分析说明:
Reserved.
openEuler评分:
4.7
Vector:CVSS:3.0/AV:L/AC:H/PR:L/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.6.0):不受影响
5.openEuler-24.03-LTS(6.6.0):不受影响
6.openEuler-24.03-LTS-Next(6.6.0):不受影响
7.openEuler-24.03-LTS-SP1(6.6.0):不受影响
修复是否涉及abi变化(是/否):
1.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.6.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):否
8.openEuler-24.03-LTS-SP1(6.6.0):否
原因说明:
1.openEuler-20.03-LTS-SP4(4.19.90):正常修复
2.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
3.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
4.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在
5.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS(6.6.0):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在
@yangyingliang ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 ,@gasonchen
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.master(6.1.0):
2.openEuler-20.03-LTS-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4(4.19.90):
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3(5.10.0):
9.openEuler-22.03-LTS-SP4:
10.openEuler-24.03-LTS:
11.openEuler-24.03-LTS-Next:
修复是否涉及abi变化(是/否):
1.master(6.1.0):
2.openEuler-20.03-LTS-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4(4.19.90):
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3(5.10.0):
9.openEuler-22.03-LTS-SP4:
10.openEuler-24.03-LTS:
11.openEuler-24.03-LTS-Next:
issue处理具体操作请参考:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。
说明:补丁链接仅供初步排查参考,实际可用性请人工再次确认,补丁下载验证可使用CVE补丁工具。
若补丁不准确,烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息,便于我们不断优化工具,不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1
@guo-mengqi 请确认分支: master,openEuler-20.03-LTS-SP1,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS,openEuler-22.03-LTS-Next,openEuler-22.03-LTS-SP1,openEuler-22.03-LTS-SP2,openEuler-22.03-LTS-SP3,openEuler-22.03-LTS-SP4,openEuler-24.03-LTS,openEuler-24.03-LTS-Next 受影响/不受影响.
请确认分支信息是否填写完整,否则将无法关闭当前issue.
@guo-mengqi 请确认分支: master,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-Next,openEuler-22.03-LTS-SP1,openEuler-22.03-LTS-SP3,openEuler-22.03-LTS-SP4,openEuler-24.03-LTS,openEuler-24.03-LTS-Next 受影响/不受影响.
请确认分支信息是否填写完整,否则将无法关闭当前issue.
@ci-robot 请确认分支: master,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-Next,openEuler-22.03-LTS-SP1,openEuler-22.03-LTS-SP3,openEuler-22.03-LTS-SP4,openEuler-24.03-LTS,openEuler-24.03-LTS-Next 受影响/不受影响.
请确认分支信息是否填写完整,否则将无法关闭当前issue.
@guo-mengqi 请确认分支: master,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-Next,openEuler-22.03-LTS-SP1,openEuler-22.03-LTS-SP3,openEuler-22.03-LTS-SP4,openEuler-24.03-LTS,openEuler-24.03-LTS-Next 受影响/不受影响.
请确认分支信息是否填写完整,否则将无法关闭当前issue.
@chenyi211 请确认分支: master,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-SP1,openEuler-22.03-LTS-SP3,openEuler-22.03-LTS-SP4,openEuler-24.03-LTS,openEuler-24.03-LTS-Next 受影响/不受影响.
请确认分支信息是否填写完整,否则将无法关闭当前issue.
CVE-2021-47468
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:
isdn: mISDN: Fix sleeping function called from invalid context
The driver can call card->isac.release() function from an atomic
context.
Fix this by calling this function after releasing the lock.
The following log reveals it:
[ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018
[ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe
[ 44.169574 ] INFO: lockdep is turned off.
[ 44.169899 ] irq event stamp: 0
[ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0
[ 44.170627 ] hardirqs last disabled at (0): [] copy_process+0x132d/0x3e00
[ 44.171240 ] softirqs last enabled at (0): [] copy_process+0x135a/0x3e00
[ 44.171852 ] softirqs last disabled at (0): [<0000000000000000>] 0x0
[ 44.172318 ] Preemption disabled at:
[ 44.172320 ] [] nj_release+0x69/0x500 [netjet]
[ 44.174441 ] Call Trace:
[ 44.174630 ] dump_stack_lvl+0xa8/0xd1
[ 44.174912 ] dump_stack+0x15/0x17
[ 44.175166 ] ___might_sleep+0x3a2/0x510
[ 44.175459 ] ? nj_release+0x69/0x500 [netjet]
[ 44.175791 ] __might_sleep+0x82/0xe0
[ 44.176063 ] ? start_flush_work+0x20/0x7b0
[ 44.176375 ] start_flush_work+0x33/0x7b0
[ 44.176672 ] ? trace_irq_enable_rcuidle+0x85/0x170
[ 44.177034 ] ? kasan_quarantine_put+0xaa/0x1f0
[ 44.177372 ] ? kasan_quarantine_put+0xaa/0x1f0
[ 44.177711 ] __flush_work+0x11a/0x1a0
[ 44.177991 ] ? flush_work+0x20/0x20
[ 44.178257 ] ? lock_release+0x13c/0x8f0
[ 44.178550 ] ? __kasan_check_write+0x14/0x20
[ 44.178872 ] ? do_raw_spin_lock+0x148/0x360
[ 44.179187 ] ? read_lock_is_recursive+0x20/0x20
[ 44.179530 ] ? __kasan_check_read+0x11/0x20
[ 44.179846 ] ? do_raw_spin_unlock+0x55/0x900
[ 44.180168 ] ? ____kasan_slab_free+0x116/0x140
[ 44.180505 ] ? _raw_spin_unlock_irqrestore+0x41/0x60
[ 44.180878 ] ? skb_queue_purge+0x1a3/0x1c0
[ 44.181189 ] ? kfree+0x13e/0x290
[ 44.181438 ] flush_work+0x17/0x20
[ 44.181695 ] mISDN_freedchannel+0xe8/0x100
[ 44.182006 ] isac_release+0x210/0x260 [mISDNipac]
[ 44.182366 ] nj_release+0xf6/0x500 [netjet]
[ 44.182685 ] nj_remove+0x48/0x70 [netjet]
[ 44.182989 ] pci_device_remove+0xa9/0x250
openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:受影响
2.openEuler-22.03-LTS-SP1:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:不受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS:受影响
7.openEuler-24.03-LTS-Next:不受影响
修复是否涉及abi变化(是/否):
1.openEuler-20.03-LTS-SP4:否
2.openEuler-22.03-LTS-SP1:否
3.openEuler-22.03-LTS-SP3:否
4.master(6.1.0):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否
===========================================================
@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
状态 | 需分析 | 内容 |
---|---|---|
已分析 | 1.影响性分析说明 | In the Linux kernel, the following vulnerability has been resolved:isdn: mISDN: Fix sleeping function called from invalid contextThe driver can call card->isac.release() function from an atomiccontext.Fix this by calling this function after releasing the lock.The following log reveals it:[ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018[ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe[ 44.169574 ] INFO: lockdep is turned off.[ 44.169899 ] irq event stamp: 0[ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0[ 44.170627 ] hardirqs last disabled at (0): [] copy_process+0x132d/0x3e00[ 44.171240 ] softirqs last enabled at (0): [] copy_process+0x135a/0x3e00[ 44.171852 ] softirqs last disabled at (0): [<0000000000000000>] 0x0[ 44.172318 ] Preemption disabled at:[ 44.172320 ] [] nj_release+0x69/0x500 [netjet][ 44.174441 ] Call Trace:[ 44.174630 ] dump_stack_lvl+0xa8/0xd1[ 44.174912 ] dump_stack+0x15/0x17[ 44.175166 ] ___might_sleep+0x3a2/0x510[ 44.175459 ] ? nj_release+0x69/0x500 [netjet][ 44.175791 ] __might_sleep+0x82/0xe0[ 44.176063 ] ? start_flush_work+0x20/0x7b0[ 44.176375 ] start_flush_work+0x33/0x7b0[ 44.176672 ] ? trace_irq_enable_rcuidle+0x85/0x170[ 44.177034 ] ? kasan_quarantine_put+0xaa/0x1f0[ 44.177372 ] ? kasan_quarantine_put+0xaa/0x1f0[ 44.177711 ] __flush_work+0x11a/0x1a0[ 44.177991 ] ? flush_work+0x20/0x20[ 44.178257 ] ? lock_release+0x13c/0x8f0[ 44.178550 ] ? __kasan_check_write+0x14/0x20[ 44.178872 ] ? do_raw_spin_lock+0x148/0x360[ 44.179187 ] ? read_lock_is_recursive+0x20/0x20[ 44.179530 ] ? __kasan_check_read+0x11/0x20[ 44.179846 ] ? do_raw_spin_unlock+0x55/0x900[ 44.180168 ] ? ____kasan_slab_free+0x116/0x140[ 44.180505 ] ? _raw_spin_unlock_irqrestore+0x41/0x60[ 44.180878 ] ? skb_queue_purge+0x1a3/0x1c0[ 44.181189 ] ? kfree+0x13e/0x290[ 44.181438 ] flush_work+0x17/0x20[ 44.181695 ] mISDN_freedchannel+0xe8/0x100[ 44.182006 ] isac_release+0x210/0x260 [mISDNipac][ 44.182366 ] nj_release+0xf6/0x500 [netjet][ 44.182685 ] nj_remove+0x48/0x70 [netjet][ 44.182989 ] pci_device_remove+0xa9/0x250 |
已分析 | 2.openEulerScore | 5.5 |
已分析 | 3.openEulerVector | AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
已分析 | 4.受影响版本排查 | openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-24.03-LTS:受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS-Next:不受影响 |
已分析 | 5.修复是否涉及abi变化 | openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
@gatieme ,@xiexiuqi ,@yangyingliang ,@pi3orama ,@jiaoff ,@guo-mengqi
关闭issue前,需要将受影响的分支在合并pr时关联上当前issue编号: #I9RC2J
受影响分支: openEuler-22.03-LTS-SP1/openEuler-22.03-LTS-SP3/openEuler-24.03-LTS
具体操作参考: https://gitee.com/help/articles/4142
CVE-2021-47468
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:
isdn: mISDN: Fix sleeping function called from invalid context
The driver can call card->isac.release() function from an atomic
context.
Fix this by calling this function after releasing the lock.
The following log reveals it:
[ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018
[ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe
[ 44.169574 ] INFO: lockdep is turned off.
[ 44.169899 ] irq event stamp: 0
[ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0
[ 44.170627 ] hardirqs last disabled at (0): [] copy_process+0x132d/0x3e00
[ 44.171240 ] softirqs last enabled at (0): [] copy_process+0x135a/0x3e00
[ 44.171852 ] softirqs last disabled at (0): [<0000000000000000>] 0x0
[ 44.172318 ] Preemption disabled at:
[ 44.172320 ] [] nj_release+0x69/0x500 [netjet]
[ 44.174441 ] Call Trace:
[ 44.174630 ] dump_stack_lvl+0xa8/0xd1
[ 44.174912 ] dump_stack+0x15/0x17
[ 44.175166 ] ___might_sleep+0x3a2/0x510
[ 44.175459 ] ? nj_release+0x69/0x500 [netjet]
[ 44.175791 ] __might_sleep+0x82/0xe0
[ 44.176063 ] ? start_flush_work+0x20/0x7b0
[ 44.176375 ] start_flush_work+0x33/0x7b0
[ 44.176672 ] ? trace_irq_enable_rcuidle+0x85/0x170
[ 44.177034 ] ? kasan_quarantine_put+0xaa/0x1f0
[ 44.177372 ] ? kasan_quarantine_put+0xaa/0x1f0
[ 44.177711 ] __flush_work+0x11a/0x1a0
[ 44.177991 ] ? flush_work+0x20/0x20
[ 44.178257 ] ? lock_release+0x13c/0x8f0
[ 44.178550 ] ? __kasan_check_write+0x14/0x20
[ 44.178872 ] ? do_raw_spin_lock+0x148/0x360
[ 44.179187 ] ? read_lock_is_recursive+0x20/0x20
[ 44.179530 ] ? __kasan_check_read+0x11/0x20
[ 44.179846 ] ? do_raw_spin_unlock+0x55/0x900
[ 44.180168 ] ? ____kasan_slab_free+0x116/0x140
[ 44.180505 ] ? _raw_spin_unlock_irqrestore+0x41/0x60
[ 44.180878 ] ? skb_queue_purge+0x1a3/0x1c0
[ 44.181189 ] ? kfree+0x13e/0x290
[ 44.181438 ] flush_work+0x17/0x20
[ 44.181695 ] mISDN_freedchannel+0xe8/0x100
[ 44.182006 ] isac_release+0x210/0x260 [mISDNipac]
[ 44.182366 ] nj_release+0xf6/0x500 [netjet]
[ 44.182685 ] nj_remove+0x48/0x70 [netjet]
[ 44.182989 ] pci_device_remove+0xa9/0x250
openEuler评分:(评分和向量)
4.7
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:受影响
2.openEuler-22.03-LTS-SP1:不受影响
3.openEuler-22.03-LTS-SP3:不受影响
4.openEuler-22.03-LTS-SP4:不受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS:不受影响
7.openEuler-24.03-LTS-Next:不受影响
修复是否涉及abi变化(是/否):
1.openEuler-20.03-LTS-SP4:否
2.openEuler-22.03-LTS-SP1:否
3.openEuler-22.03-LTS-SP3:否
4.master(6.1.0):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否
CVE-2021-47468
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:
isdn: mISDN: Fix sleeping function called from invalid context
The driver can call card->isac.release() function from an atomic
context.
Fix this by calling this function after releasing the lock.
The following log reveals it:
[ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018
[ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe
[ 44.169574 ] INFO: lockdep is turned off.
[ 44.169899 ] irq event stamp: 0
[ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0
[ 44.170627 ] hardirqs last disabled at (0): [] copy_process+0x132d/0x3e00
[ 44.171240 ] softirqs last enabled at (0): [] copy_process+0x135a/0x3e00
[ 44.171852 ] softirqs last disabled at (0): [<0000000000000000>] 0x0
[ 44.172318 ] Preemption disabled at:
[ 44.172320 ] [] nj_release+0x69/0x500 [netjet]
[ 44.174441 ] Call Trace:
[ 44.174630 ] dump_stack_lvl+0xa8/0xd1
[ 44.174912 ] dump_stack+0x15/0x17
[ 44.175166 ] ___might_sleep+0x3a2/0x510
[ 44.175459 ] ? nj_release+0x69/0x500 [netjet]
[ 44.175791 ] __might_sleep+0x82/0xe0
[ 44.176063 ] ? start_flush_work+0x20/0x7b0
[ 44.176375 ] start_flush_work+0x33/0x7b0
[ 44.176672 ] ? trace_irq_enable_rcuidle+0x85/0x170
[ 44.177034 ] ? kasan_quarantine_put+0xaa/0x1f0
[ 44.177372 ] ? kasan_quarantine_put+0xaa/0x1f0
[ 44.177711 ] __flush_work+0x11a/0x1a0
[ 44.177991 ] ? flush_work+0x20/0x20
[ 44.178257 ] ? lock_release+0x13c/0x8f0
[ 44.178550 ] ? __kasan_check_write+0x14/0x20
[ 44.178872 ] ? do_raw_spin_lock+0x148/0x360
[ 44.179187 ] ? read_lock_is_recursive+0x20/0x20
[ 44.179530 ] ? __kasan_check_read+0x11/0x20
[ 44.179846 ] ? do_raw_spin_unlock+0x55/0x900
[ 44.180168 ] ? ____kasan_slab_free+0x116/0x140
[ 44.180505 ] ? _raw_spin_unlock_irqrestore+0x41/0x60
[ 44.180878 ] ? skb_queue_purge+0x1a3/0x1c0
[ 44.181189 ] ? kfree+0x13e/0x290
[ 44.181438 ] flush_work+0x17/0x20
[ 44.181695 ] mISDN_freedchannel+0xe8/0x100
[ 44.182006 ] isac_release+0x210/0x260 [mISDNipac]
[ 44.182366 ] nj_release+0xf6/0x500 [netjet]
[ 44.182685 ] nj_remove+0x48/0x70 [netjet]
[ 44.182989 ] pci_device_remove+0xa9/0x250
openEuler评分:(评分和向量)
4.7
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:受影响
2.openEuler-22.03-LTS-SP1:不受影响
3.openEuler-22.03-LTS-SP3:不受影响
4.openEuler-22.03-LTS-SP4:不受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS:不受影响
7.openEuler-24.03-LTS-Next:不受影响
修复是否涉及abi变化(是/否):
1.openEuler-20.03-LTS-SP4:否
2.openEuler-22.03-LTS-SP1:否
3.openEuler-22.03-LTS-SP3:否
4.master(6.1.0):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否
@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
状态 | 需分析 | 内容 |
---|---|---|
已分析 | 1.影响性分析说明 | In the Linux kernel, the following vulnerability has been resolved:isdn: mISDN: Fix sleeping function called from invalid contextThe driver can call card->isac.release() function from an atomiccontext.Fix this by calling this function after releasing the lock.The following log reveals it:[ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018[ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe[ 44.169574 ] INFO: lockdep is turned off.[ 44.169899 ] irq event stamp: 0[ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0[ 44.170627 ] hardirqs last disabled at (0): [] copy_process+0x132d/0x3e00[ 44.171240 ] softirqs last enabled at (0): [] copy_process+0x135a/0x3e00[ 44.171852 ] softirqs last disabled at (0): [<0000000000000000>] 0x0[ 44.172318 ] Preemption disabled at:[ 44.172320 ] [] nj_release+0x69/0x500 [netjet][ 44.174441 ] Call Trace:[ 44.174630 ] dump_stack_lvl+0xa8/0xd1[ 44.174912 ] dump_stack+0x15/0x17[ 44.175166 ] ___might_sleep+0x3a2/0x510[ 44.175459 ] ? nj_release+0x69/0x500 [netjet][ 44.175791 ] __might_sleep+0x82/0xe0[ 44.176063 ] ? start_flush_work+0x20/0x7b0[ 44.176375 ] start_flush_work+0x33/0x7b0[ 44.176672 ] ? trace_irq_enable_rcuidle+0x85/0x170[ 44.177034 ] ? kasan_quarantine_put+0xaa/0x1f0[ 44.177372 ] ? kasan_quarantine_put+0xaa/0x1f0[ 44.177711 ] __flush_work+0x11a/0x1a0[ 44.177991 ] ? flush_work+0x20/0x20[ 44.178257 ] ? lock_release+0x13c/0x8f0[ 44.178550 ] ? __kasan_check_write+0x14/0x20[ 44.178872 ] ? do_raw_spin_lock+0x148/0x360[ 44.179187 ] ? read_lock_is_recursive+0x20/0x20[ 44.179530 ] ? __kasan_check_read+0x11/0x20[ 44.179846 ] ? do_raw_spin_unlock+0x55/0x900[ 44.180168 ] ? ____kasan_slab_free+0x116/0x140[ 44.180505 ] ? _raw_spin_unlock_irqrestore+0x41/0x60[ 44.180878 ] ? skb_queue_purge+0x1a3/0x1c0[ 44.181189 ] ? kfree+0x13e/0x290[ 44.181438 ] flush_work+0x17/0x20[ 44.181695 ] mISDN_freedchannel+0xe8/0x100[ 44.182006 ] isac_release+0x210/0x260 [mISDNipac][ 44.182366 ] nj_release+0xf6/0x500 [netjet][ 44.182685 ] nj_remove+0x48/0x70 [netjet][ 44.182989 ] pci_device_remove+0xa9/0x250 |
已分析 | 2.openEulerScore | 4.7 |
已分析 | 3.openEulerVector | AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
已分析 | 4.受影响版本排查 | openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响 |
已分析 | 5.修复是否涉及abi变化 | openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
CVE-2021-47468
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:
isdn: mISDN: Fix sleeping function called from invalid context
The driver can call card->isac.release() function from an atomic
context.
Fix this by calling this function after releasing the lock.
The following log reveals it:
[ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018
[ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe
[ 44.169574 ] INFO: lockdep is turned off.
[ 44.169899 ] irq event stamp: 0
[ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0
[ 44.170627 ] hardirqs last disabled at (0): [] copy_process+0x132d/0x3e00
[ 44.171240 ] softirqs last enabled at (0): [] copy_process+0x135a/0x3e00
[ 44.171852 ] softirqs last disabled at (0): [<0000000000000000>] 0x0
[ 44.172318 ] Preemption disabled at:
[ 44.172320 ] [] nj_release+0x69/0x500 [netjet]
[ 44.174441 ] Call Trace:
[ 44.174630 ] dump_stack_lvl+0xa8/0xd1
[ 44.174912 ] dump_stack+0x15/0x17
[ 44.175166 ] ___might_sleep+0x3a2/0x510
[ 44.175459 ] ? nj_release+0x69/0x500 [netjet]
[ 44.175791 ] __might_sleep+0x82/0xe0
[ 44.176063 ] ? start_flush_work+0x20/0x7b0
[ 44.176375 ] start_flush_work+0x33/0x7b0
[ 44.176672 ] ? trace_irq_enable_rcuidle+0x85/0x170
[ 44.177034 ] ? kasan_quarantine_put+0xaa/0x1f0
[ 44.177372 ] ? kasan_quarantine_put+0xaa/0x1f0
[ 44.177711 ] __flush_work+0x11a/0x1a0
[ 44.177991 ] ? flush_work+0x20/0x20
[ 44.178257 ] ? lock_release+0x13c/0x8f0
[ 44.178550 ] ? __kasan_check_write+0x14/0x20
[ 44.178872 ] ? do_raw_spin_lock+0x148/0x360
[ 44.179187 ] ? read_lock_is_recursive+0x20/0x20
[ 44.179530 ] ? __kasan_check_read+0x11/0x20
[ 44.179846 ] ? do_raw_spin_unlock+0x55/0x900
[ 44.180168 ] ? ____kasan_slab_free+0x116/0x140
[ 44.180505 ] ? _raw_spin_unlock_irqrestore+0x41/0x60
[ 44.180878 ] ? skb_queue_purge+0x1a3/0x1c0
[ 44.181189 ] ? kfree+0x13e/0x290
[ 44.181438 ] flush_work+0x17/0x20
[ 44.181695 ] mISDN_freedchannel+0xe8/0x100
[ 44.182006 ] isac_release+0x210/0x260 [mISDNipac]
[ 44.182366 ] nj_release+0xf6/0x500 [netjet]
[ 44.182685 ] nj_remove+0x48/0x70 [netjet]
[ 44.182989 ] pci_device_remove+0xa9/0x250
openEuler评分:(评分和向量)
4.7
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:受影响
2.openEuler-22.03-LTS-SP1:不受影响
3.openEuler-22.03-LTS-SP3:不受影响
4.openEuler-22.03-LTS-SP4:不受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS:不受影响
7.openEuler-24.03-LTS-Next:不受影响
修复是否涉及abi变化(是/否):
1.openEuler-20.03-LTS-SP4:否
2.openEuler-22.03-LTS-SP1:否
3.openEuler-22.03-LTS-SP3:否
4.master(6.1.0):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否
@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
状态 | 需分析 | 内容 |
---|---|---|
已分析 | 1.影响性分析说明 | In the Linux kernel, the following vulnerability has been resolved:isdn: mISDN: Fix sleeping function called from invalid contextThe driver can call card->isac.release() function from an atomiccontext.Fix this by calling this function after releasing the lock.The following log reveals it:[ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018[ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe[ 44.169574 ] INFO: lockdep is turned off.[ 44.169899 ] irq event stamp: 0[ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0[ 44.170627 ] hardirqs last disabled at (0): [] copy_process+0x132d/0x3e00[ 44.171240 ] softirqs last enabled at (0): [] copy_process+0x135a/0x3e00[ 44.171852 ] softirqs last disabled at (0): [<0000000000000000>] 0x0[ 44.172318 ] Preemption disabled at:[ 44.172320 ] [] nj_release+0x69/0x500 [netjet][ 44.174441 ] Call Trace:[ 44.174630 ] dump_stack_lvl+0xa8/0xd1[ 44.174912 ] dump_stack+0x15/0x17[ 44.175166 ] ___might_sleep+0x3a2/0x510[ 44.175459 ] ? nj_release+0x69/0x500 [netjet][ 44.175791 ] __might_sleep+0x82/0xe0[ 44.176063 ] ? start_flush_work+0x20/0x7b0[ 44.176375 ] start_flush_work+0x33/0x7b0[ 44.176672 ] ? trace_irq_enable_rcuidle+0x85/0x170[ 44.177034 ] ? kasan_quarantine_put+0xaa/0x1f0[ 44.177372 ] ? kasan_quarantine_put+0xaa/0x1f0[ 44.177711 ] __flush_work+0x11a/0x1a0[ 44.177991 ] ? flush_work+0x20/0x20[ 44.178257 ] ? lock_release+0x13c/0x8f0[ 44.178550 ] ? __kasan_check_write+0x14/0x20[ 44.178872 ] ? do_raw_spin_lock+0x148/0x360[ 44.179187 ] ? read_lock_is_recursive+0x20/0x20[ 44.179530 ] ? __kasan_check_read+0x11/0x20[ 44.179846 ] ? do_raw_spin_unlock+0x55/0x900[ 44.180168 ] ? ____kasan_slab_free+0x116/0x140[ 44.180505 ] ? _raw_spin_unlock_irqrestore+0x41/0x60[ 44.180878 ] ? skb_queue_purge+0x1a3/0x1c0[ 44.181189 ] ? kfree+0x13e/0x290[ 44.181438 ] flush_work+0x17/0x20[ 44.181695 ] mISDN_freedchannel+0xe8/0x100[ 44.182006 ] isac_release+0x210/0x260 [mISDNipac][ 44.182366 ] nj_release+0xf6/0x500 [netjet][ 44.182685 ] nj_remove+0x48/0x70 [netjet][ 44.182989 ] pci_device_remove+0xa9/0x250 |
已分析 | 2.openEulerScore | 4.7 |
已分析 | 3.openEulerVector | AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
已分析 | 4.受影响版本排查 | openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响 |
已分析 | 5.修复是否涉及abi变化 | openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
状态 | 需分析 | 内容 |
---|---|---|
已分析 | 1.影响性分析说明 | In the Linux kernel, the following vulnerability has been resolved:isdn: mISDN: Fix sleeping function called from invalid contextThe driver can call card->isac.release() function from an atomiccontext.Fix this by calling this function after releasing the lock.The following log reveals it:[ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018[ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe[ 44.169574 ] INFO: lockdep is turned off.[ 44.169899 ] irq event stamp: 0[ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0[ 44.170627 ] hardirqs last disabled at (0): [] copy_process+0x132d/0x3e00[ 44.171240 ] softirqs last enabled at (0): [] copy_process+0x135a/0x3e00[ 44.171852 ] softirqs last disabled at (0): [<0000000000000000>] 0x0[ 44.172318 ] Preemption disabled at:[ 44.172320 ] [] nj_release+0x69/0x500 [netjet][ 44.174441 ] Call Trace:[ 44.174630 ] dump_stack_lvl+0xa8/0xd1[ 44.174912 ] dump_stack+0x15/0x17[ 44.175166 ] ___might_sleep+0x3a2/0x510[ 44.175459 ] ? nj_release+0x69/0x500 [netjet][ 44.175791 ] __might_sleep+0x82/0xe0[ 44.176063 ] ? start_flush_work+0x20/0x7b0[ 44.176375 ] start_flush_work+0x33/0x7b0[ 44.176672 ] ? trace_irq_enable_rcuidle+0x85/0x170[ 44.177034 ] ? kasan_quarantine_put+0xaa/0x1f0[ 44.177372 ] ? kasan_quarantine_put+0xaa/0x1f0[ 44.177711 ] __flush_work+0x11a/0x1a0[ 44.177991 ] ? flush_work+0x20/0x20[ 44.178257 ] ? lock_release+0x13c/0x8f0[ 44.178550 ] ? __kasan_check_write+0x14/0x20[ 44.178872 ] ? do_raw_spin_lock+0x148/0x360[ 44.179187 ] ? read_lock_is_recursive+0x20/0x20[ 44.179530 ] ? __kasan_check_read+0x11/0x20[ 44.179846 ] ? do_raw_spin_unlock+0x55/0x900[ 44.180168 ] ? ____kasan_slab_free+0x116/0x140[ 44.180505 ] ? _raw_spin_unlock_irqrestore+0x41/0x60[ 44.180878 ] ? skb_queue_purge+0x1a3/0x1c0[ 44.181189 ] ? kfree+0x13e/0x290[ 44.181438 ] flush_work+0x17/0x20[ 44.181695 ] mISDN_freedchannel+0xe8/0x100[ 44.182006 ] isac_release+0x210/0x260 [mISDNipac][ 44.182366 ] nj_release+0xf6/0x500 [netjet][ 44.182685 ] nj_remove+0x48/0x70 [netjet][ 44.182989 ] pci_device_remove+0xa9/0x250 |
已分析 | 2.openEulerScore | 4.7 |
已分析 | 3.openEulerVector | AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
已分析 | 4.受影响版本排查 | openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响 |
已分析 | 5.修复是否涉及abi变化 | openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
CVE-2021-47468
影响性分析说明:
Reserved.
openEuler评分:(评分和向量)
3.9
CVSS: 3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:受影响
2.openEuler-22.03-LTS-SP3:不受影响
3.openEuler-22.03-LTS-SP4:不受影响
4.master(6.6.0):不受影响
5.openEuler-24.03-LTS:不受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:不受影响
原因说明:
1.openEuler-20.03-LTS-SP4:正常修复
2.openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在
4.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS:不受影响-漏洞代码不存在
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在
修复是否涉及abi变化(是/否):
1.openEuler-20.03-LTS-SP4:否
2.openEuler-22.03-LTS-SP1:否
3.openEuler-22.03-LTS-SP3:否
4.master(23.08.5):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否
8.openEuler-24.03-LTS-SP1:否
===========================================================
@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
状态 | 分析项目 | 内容 |
---|---|---|
已分析 | 1.影响性分析说明 | Reserved. |
已分析 | 2.openEulerScore | 3.9 |
已分析 | 3.openEulerVector | AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L |
已分析 | 4.受影响版本排查 | openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:不受影响 |
已分析 | 5.是否涉及abi变化 | openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS-SP1:否 |
已分析 | 6.原因说明 | openEuler-20.03-LTS-SP4:正常修复,master:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-24.03-LTS:不受影响-漏洞代码不存在,openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
状态 | 分析项目 | 内容 |
---|---|---|
已分析 | 1.影响性分析说明 | Reserved. |
已分析 | 2.openEulerScore | 4.7 |
已分析 | 3.openEulerVector | AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
已分析 | 4.受影响版本排查 | openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:不受影响 |
已分析 | 5.是否涉及abi变化 | openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS-SP1:否 |
已分析 | 6.原因说明 | openEuler-20.03-LTS-SP4:正常修复,master:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-24.03-LTS:不受影响-漏洞代码不存在,openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
登录 后才可以发表评论
FileDragTip