一、漏洞信息
漏洞编号:CVE-2022-49034
漏洞归属组件: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:0.0 None
Vector:CVSS:3.0/
漏洞简述:
In the Linux kernel, the following vulnerability has been resolved:sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACKWhen CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected,cpu_max_bits_warn() generates a runtime warning similar as below whenshowing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)instead of NR_CPUS to iterate CPUs.[ 3.052463] ------------[ cut here ]------------[ 3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0[ 3.070072] Modules linked in: efivarfs autofs4[ 3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052[ 3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000[ 3.109127] 9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430[ 3.118774] 90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff[ 3.128412] 0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890[ 3.138056] 0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa[ 3.147711] ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000[ 3.157364] 900000000101c998 0000000000000004 9000000000ef7430 0000000000000000[ 3.167012] 0000000000000009 000000000000006c 0000000000000000 0000000000000000[ 3.176641] 9000000000d3de08 9000000001639390 90000000002086d8 00007ffff0080286[ 3.186260] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c[ 3.195868] ...[ 3.199917] Call Trace:[ 3.203941] [<90000000002086d8>] show_stack+0x38/0x14c[ 3.210666] [<9000000000cf846c>] dump_stack_lvl+0x60/0x88[ 3.217625] [<900000000023d268>] __warn+0xd0/0x100[ 3.223958] [<9000000000cf3c90>] warn_slowpath_fmt+0x7c/0xcc[ 3.231150] [<9000000000210220>] show_cpuinfo+0x5e8/0x5f0[ 3.238080] [<90000000004f578c>] seq_read_iter+0x354/0x4b4[ 3.245098] [<90000000004c2e90>] new_sync_read+0x17c/0x1c4[ 3.252114] [<90000000004c5174>] vfs_read+0x138/0x1d0[ 3.258694] [<90000000004c55f8>] ksys_read+0x70/0x100[ 3.265265] [<9000000000cfde9c>] do_syscall+0x7c/0x94[ 3.271820] [<9000000000202fe4>] handle_syscall+0xc4/0x160[ 3.281824] ---[ end trace 8b484262b4b8c24c ]---
漏洞公开时间:2024-12-27 22:15:22
漏洞创建时间:2024-12-27 22:43:06
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2022-49034
漏洞分析指导链接:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息:
无
二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACKWhen CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected,cpu_max_bits_warn() generates a runtime warning similar as below whenshowing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)instead of NR_CPUS to iterate CPUs.[ 3.052463] ------------[ cut here ]------------[ 3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0[ 3.070072] Modules linked in: efivarfs autofs4[ 3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052[ 3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000[ 3.109127] 9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430[ 3.118774] 90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff[ 3.128412] 0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890[ 3.138056] 0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa[ 3.147711] ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000[ 3.157364] 900000000101c998 0000000000000004 9000000000ef7430 0000000000000000[ 3.167012] 0000000000000009 000000000000006c 0000000000000000 0000000000000000[ 3.176641] 9000000000d3de08 9000000001639390 90000000002086d8 00007ffff0080286[ 3.186260] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c[ 3.195868] ...[ 3.199917] Call Trace:[ 3.203941] [<90000000002086d8>] show_stack+0x38/0x14c[ 3.210666] [<9000000000cf846c>] dump_stack_lvl+0x60/0x88[ 3.217625] [<900000000023d268>] __warn+0xd0/0x100[ 3.223958] [<9000000000cf3c90>] warn_slowpath_fmt+0x7c/0xcc[ 3.231150] [<9000000000210220>] show_cpuinfo+0x5e8/0x5f0[ 3.238080] [<90000000004f578c>] seq_read_iter+0x354/0x4b4[ 3.245098] [<90000000004c2e90>] new_sync_read+0x17c/0x1c4[ 3.252114] [<90000000004c5174>] vfs_read+0x138/0x1d0[ 3.258694] [<90000000004c55f8>] ksys_read+0x70/0x100[ 3.265265] [<9000000000cfde9c>] do_syscall+0x7c/0x94[ 3.271820] [<9000000000202fe4>] handle_syscall+0xc4/0x160[ 3.281824] ---[ end trace 8b484262b4b8c24c ]---The Linux kernel CVE team has assigned CVE-2022-49034 to this issue.
openEuler评分:
3.9
Vector:CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4(4.19.90):受影响
2.openEuler-22.03-LTS-SP1:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-SP1:受影响
7.master:不受影响
8.openEuler-24.03-LTS-Next:不受影响
修复是否涉及abi变化(是/否):
1.openEuler-20.03-LTS-SP4(4.19.90):否
2.openEuler-22.03-LTS-SP1:否
3.openEuler-22.03-LTS-SP3:否
4.master:否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否
8.openEuler-24.03-LTS-SP1:否
原因说明:
1.openEuler-20.03-LTS-SP4(4.19.90):正常修复
2.openEuler-22.03-LTS-SP1:正常修复
3.openEuler-22.03-LTS-SP3:正常修复
4.openEuler-22.03-LTS-SP4:正常修复
5.openEuler-24.03-LTS:正常修复
6.openEuler-24.03-LTS-SP1:正常修复
7.master:不受影响-漏洞代码不能被攻击者触发
8.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
三、漏洞修复
安全公告链接:https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-1037
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。
@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.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP1(5.10.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-Next(6.6.0):
8.openEuler-24.03-LTS-SP1(6.6.0):
修复是否涉及abi变化(是/否):
1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP1(5.10.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-Next(6.6.0):
8.openEuler-24.03-LTS-SP1(6.6.0):
原因说明:
1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP1(5.10.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-Next(6.6.0):
8.openEuler-24.03-LTS-SP1(6.6.0):
原因说明填写请参考下方表格(注意:版本是否受影响和版本的原因说明必须对应,例如master版本分支受影响,那原因说明只能是受影响对应的原因之一!):
分支状态 | 原因说明 |
---|---|
受影响 | 正常修复 |
受影响 | 暂不修复-漏洞仍在分析中 |
受影响 | 暂不修复-暂无解决方案或补丁 |
受影响 | 暂不修复-待升级版本修复 |
受影响 | 不修复-超出修复范围 |
受影响 | 不修复-特殊原因导致不再修复 |
不受影响 | 不受影响-组件不存在 |
不受影响 | 不受影响-已有内置的内联控制或缓解措施 |
不受影响 | 不受影响-漏洞代码不能被攻击者触发 |
不受影响 | 不受影响-漏洞代码不在执行路径 |
不受影响 | 不受影响-漏洞代码不存在 |
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-2022-49034
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:
sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected,
cpu_max_bits_warn() generates a runtime warning similar as below when
showing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)
instead of NR_CPUS to iterate CPUs.
[ 3.052463] ------------[ cut here ]------------
[ 3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0
[ 3.070072] Modules linked in: efivarfs autofs4
[ 3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052
[ 3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000
[ 3.109127] 9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430
[ 3.118774] 90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff
[ 3.128412] 0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890
[ 3.138056] 0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa
[ 3.147711] ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000
[ 3.157364] 900000000101c998 0000000000000004 9000000000ef7430 0000000000000000
[ 3.167012] 0000000000000009 000000000000006c 0000000000000000 0000000000000000
[ 3.176641] 9000000000d3de08 9000000001639390 90000000002086d8 00007ffff0080286
[ 3.186260] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c
[ 3.195868] ...
[ 3.199917] Call Trace:
[ 3.203941] [<90000000002086d8>] show_stack+0x38/0x14c
[ 3.210666] [<9000000000cf846c>] dump_stack_lvl+0x60/0x88
[ 3.217625] [<900000000023d268>] __warn+0xd0/0x100
[ 3.223958] [<9000000000cf3c90>] warn_slowpath_fmt+0x7c/0xcc
[ 3.231150] [<9000000000210220>] show_cpuinfo+0x5e8/0x5f0
[ 3.238080] [<90000000004f578c>] seq_read_iter+0x354/0x4b4
[ 3.245098] [<90000000004c2e90>] new_sync_read+0x17c/0x1c4
[ 3.252114] [<90000000004c5174>] vfs_read+0x138/0x1d0
[ 3.258694] [<90000000004c55f8>] ksys_read+0x70/0x100
[ 3.265265] [<9000000000cfde9c>] do_syscall+0x7c/0x94
[ 3.271820] [<9000000000202fe4>] handle_syscall+0xc4/0x160
[ 3.281824] ---[ end trace 8b484262b4b8c24c ]---
The Linux kernel CVE team has assigned CVE-2022-49034 to this issue.
openEuler评分:(评分和向量)
3.9
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-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:不受影响
8.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(6.1.0):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否
8.openEuler-24.03-LTS-SP1:否
原因说明:
1.master(23.08.5):不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:正常修复
3.openEuler-22.03-LTS-SP1:正常修复
4.openEuler-22.03-LTS-SP3:正常修复
5.openEuler-22.03-LTS-SP4:正常修复
6.openEuler-24.03-LTS:正常修复
7.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
8.openEuler-24.03-LTS-SP1:正常修复
@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
状态 | 分析项目 | 内容 |
---|---|---|
已分析 | 1.影响性分析说明 | In the Linux kernel, the following vulnerability has been resolved:sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACKWhen CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected,cpu_max_bits_warn() generates a runtime warning similar as below whenshowing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)instead of NR_CPUS to iterate CPUs.[ 3.052463] ------------[ cut here ]------------[ 3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0[ 3.070072] Modules linked in: efivarfs autofs4[ 3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052[ 3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000[ 3.109127] 9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430[ 3.118774] 90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff[ 3.128412] 0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890[ 3.138056] 0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa[ 3.147711] ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000[ 3.157364] 900000000101c998 0000000000000004 9000000000ef7430 0000000000000000[ 3.167012] 0000000000000009 000000000000006c 0000000000000000 0000000000000000[ 3.176641] 9000000000d3de08 9000000001639390 90000000002086d8 00007ffff0080286[ 3.186260] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c[ 3.195868] ...[ 3.199917] Call Trace:[ 3.203941] [<90000000002086d8>] show_stack+0x38/0x14c[ 3.210666] [<9000000000cf846c>] dump_stack_lvl+0x60/0x88[ 3.217625] [<900000000023d268>] __warn+0xd0/0x100[ 3.223958] [<9000000000cf3c90>] warn_slowpath_fmt+0x7c/0xcc[ 3.231150] [<9000000000210220>] show_cpuinfo+0x5e8/0x5f0[ 3.238080] [<90000000004f578c>] seq_read_iter+0x354/0x4b4[ 3.245098] [<90000000004c2e90>] new_sync_read+0x17c/0x1c4[ 3.252114] [<90000000004c5174>] vfs_read+0x138/0x1d0[ 3.258694] [<90000000004c55f8>] ksys_read+0x70/0x100[ 3.265265] [<9000000000cfde9c>] do_syscall+0x7c/0x94[ 3.271820] [<9000000000202fe4>] handle_syscall+0xc4/0x160[ 3.281824] ---[ end trace 8b484262b4b8c24c ]---The Linux kernel CVE team has assigned CVE-2022-49034 to this issue. |
已分析 | 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-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-SP1:受影响,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:否,openEuler-24.03-LTS-SP1:否 |
已分析 | 6.原因说明 | 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-SP1:正常修复,master:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
登录 后才可以发表评论