登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
模力方舟
AI 队友
登录
注册
轻量养虾,开箱即用!低 Token + 稳定算力,Gitee & 模力方舟联合出品的 PocketClaw 正式开售!点击了解详情
代码拉取完成,页面将自动刷新
仓库状态说明
开源项目
>
其他开源
>
操作系统
&&
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
128
Star
73
Fork
330
src-openEuler
/
kernel
关闭
代码
Issues
1197
Pull Requests
35
Wiki
统计
流水线
服务
JavaDoc
PHPDoc
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
SBOM
开发画像分析
我知道了,不再自动展开
更新失败,请稍后重试!
移除标识
内容风险标识
本任务被
标识为内容中包含有代码安全 Bug 、隐私泄露等敏感信息,仓库外成员不可访问
CVE-2022-48808
已拒绝
#IADGMV
CVE和安全问题
openeuler-ci-bot
拥有者
创建于
2024-07-17 00:00
一、漏洞信息 漏洞编号:[CVE-2022-48808](https://nvd.nist.gov/vuln/detail/CVE-2022-48808) 漏洞归属组件:[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 None Vector:CVSS:2.0/ 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:net: dsa: fix panic when DSA master device unbinds on shutdownRafael reports that on a system with LX2160A and Marvell DSA switches,if a reboot occurs while the DSA master (dpaa2-eth) is up, the followingpanic can be seen:systemd-shutdown[1]: Rebooting.Unable to handle kernel paging request at virtual address 00a0000800000041[00a0000800000041] address between user and kernel address rangesInternal error: Oops: 96000004 [#1] PREEMPT SMPCPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32pc : dsa_slave_netdevice_event+0x130/0x3e4lr : raw_notifier_call_chain+0x50/0x6cCall trace: dsa_slave_netdevice_event+0x130/0x3e4 raw_notifier_call_chain+0x50/0x6c call_netdevice_notifiers_info+0x54/0xa0 __dev_close_many+0x50/0x130 dev_close_many+0x84/0x120 unregister_netdevice_many+0x130/0x710 unregister_netdevice_queue+0x8c/0xd0 unregister_netdev+0x20/0x30 dpaa2_eth_remove+0x68/0x190 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver_internal+0xac/0xb0 device_links_unbind_consumers+0xd4/0x100 __device_release_driver+0x94/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_device_remove+0x24/0x40 __fsl_mc_device_remove+0xc/0x20 device_for_each_child+0x58/0xa0 dprc_remove+0x90/0xb0 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_bus_remove+0x80/0x100 fsl_mc_bus_shutdown+0xc/0x1c platform_shutdown+0x20/0x30 device_shutdown+0x154/0x330 __do_sys_reboot+0x1cc/0x250 __arm64_sys_reboot+0x20/0x30 invoke_syscall.constprop.0+0x4c/0xe0 do_el0_svc+0x4c/0x150 el0_svc+0x24/0xb0 el0t_64_sync_handler+0xa8/0xb0 el0t_64_sync+0x178/0x17cIt can be seen from the stack trace that the problem is that thederegistration of the master causes a dev_close(), which gets notifiedas NETDEV_GOING_DOWN to dsa_slave_netdevice_event().But dsa_switch_shutdown() has already run, and this has unregistered theDSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts tocall dev_close_many() on those slave interfaces, leading to the problem.The previous attempt to avoid the NETDEV_GOING_DOWN on the master afterdsa_switch_shutdown() was called seems improper. Unregistering the slaveinterfaces is unnecessary and unhelpful. Instead, after the slaves havestopped being uppers of the DSA master, we can now reset to NULL themaster->dsa_ptr pointer, which will make DSA start ignoring all futurenotifier events on the master. 漏洞公开时间:2024-07-16 20:15:05 漏洞创建时间:2024-07-17 00:00:20 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2022-48808 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48808 | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-48808.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | suse_bugzilla | https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5 | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | suse_bugzilla | https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7 | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | suse_bugzilla | https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2022-48808 | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2022-48808 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://git.kernel.org/linus/ee534378f00561207656663d93907583958339ae (5.17-rc4) | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://ubuntu.com/security/notices/USN-6917-1 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://ubuntu.com/security/notices/USN-6919-1 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://ubuntu.com/security/notices/USN-6927-1 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2022-48808 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2022-48808 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2022-48808 | https://ubuntu.com/security/CVE-2022-48808 | </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/ee534378f00561207656663d93907583958339ae | https://git.kernel.org/linus/0650bf52b31ff35dc6430fc2e37969c36baba724 | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明: openEuler评分: 受影响版本排查(受影响/不受影响): 1.master(6.1.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): 修复是否涉及abi变化(是/否): 1.master(6.1.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):
一、漏洞信息 漏洞编号:[CVE-2022-48808](https://nvd.nist.gov/vuln/detail/CVE-2022-48808) 漏洞归属组件:[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 None Vector:CVSS:2.0/ 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:net: dsa: fix panic when DSA master device unbinds on shutdownRafael reports that on a system with LX2160A and Marvell DSA switches,if a reboot occurs while the DSA master (dpaa2-eth) is up, the followingpanic can be seen:systemd-shutdown[1]: Rebooting.Unable to handle kernel paging request at virtual address 00a0000800000041[00a0000800000041] address between user and kernel address rangesInternal error: Oops: 96000004 [#1] PREEMPT SMPCPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32pc : dsa_slave_netdevice_event+0x130/0x3e4lr : raw_notifier_call_chain+0x50/0x6cCall trace: dsa_slave_netdevice_event+0x130/0x3e4 raw_notifier_call_chain+0x50/0x6c call_netdevice_notifiers_info+0x54/0xa0 __dev_close_many+0x50/0x130 dev_close_many+0x84/0x120 unregister_netdevice_many+0x130/0x710 unregister_netdevice_queue+0x8c/0xd0 unregister_netdev+0x20/0x30 dpaa2_eth_remove+0x68/0x190 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver_internal+0xac/0xb0 device_links_unbind_consumers+0xd4/0x100 __device_release_driver+0x94/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_device_remove+0x24/0x40 __fsl_mc_device_remove+0xc/0x20 device_for_each_child+0x58/0xa0 dprc_remove+0x90/0xb0 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_bus_remove+0x80/0x100 fsl_mc_bus_shutdown+0xc/0x1c platform_shutdown+0x20/0x30 device_shutdown+0x154/0x330 __do_sys_reboot+0x1cc/0x250 __arm64_sys_reboot+0x20/0x30 invoke_syscall.constprop.0+0x4c/0xe0 do_el0_svc+0x4c/0x150 el0_svc+0x24/0xb0 el0t_64_sync_handler+0xa8/0xb0 el0t_64_sync+0x178/0x17cIt can be seen from the stack trace that the problem is that thederegistration of the master causes a dev_close(), which gets notifiedas NETDEV_GOING_DOWN to dsa_slave_netdevice_event().But dsa_switch_shutdown() has already run, and this has unregistered theDSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts tocall dev_close_many() on those slave interfaces, leading to the problem.The previous attempt to avoid the NETDEV_GOING_DOWN on the master afterdsa_switch_shutdown() was called seems improper. Unregistering the slaveinterfaces is unnecessary and unhelpful. Instead, after the slaves havestopped being uppers of the DSA master, we can now reset to NULL themaster->dsa_ptr pointer, which will make DSA start ignoring all futurenotifier events on the master. 漏洞公开时间:2024-07-16 20:15:05 漏洞创建时间:2024-07-17 00:00:20 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2022-48808 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48808 | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-48808.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | suse_bugzilla | https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5 | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | suse_bugzilla | https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7 | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | suse_bugzilla | https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2022-48808 | https://bugzilla.suse.com/show_bug.cgi?id=1227958 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2022-48808 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://git.kernel.org/linus/ee534378f00561207656663d93907583958339ae (5.17-rc4) | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://ubuntu.com/security/notices/USN-6917-1 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://ubuntu.com/security/notices/USN-6919-1 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://ubuntu.com/security/notices/USN-6927-1 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2022-48808 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2022-48808 | https://ubuntu.com/security/CVE-2022-48808 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2022-48808 | https://ubuntu.com/security/CVE-2022-48808 | </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/ee534378f00561207656663d93907583958339ae | https://git.kernel.org/linus/0650bf52b31ff35dc6430fc2e37969c36baba724 | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明: openEuler评分: 受影响版本排查(受影响/不受影响): 1.master(6.1.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): 修复是否涉及abi变化(是/否): 1.master(6.1.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):
评论 (
5
)
登录
后才可以发表评论
状态
已拒绝
待办的
已挂起
进行中
已完成
已拒绝
负责人
未设置
标签
CVE/UNFIXED
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 帐号,请先登录后再操作。
立即登录
没有帐号,去注册