CVE-2024-50136

一、漏洞信息
漏洞编号：CVE-2024-50136
漏洞归属组件：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：5.5 Medium
Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
漏洞简述：
In the Linux kernel, the following vulnerability has been resolved:net/mlx5: Unregister notifier on eswitch init failureIt otherwise remains registered and a subsequent attempt at eswitchenabling might trigger warnings of the sort:[ 682.589148] ------------[ cut here ]------------[ 682.590204] notifier callback eswitch_vport_event [mlx5_core] already registered[ 682.590256] WARNING: CPU: 13 PID: 2660 at kernel/notifier.c:31 notifier_chain_register+0x3e/0x90[...snipped][ 682.610052] Call Trace:[ 682.610369] [ 682.610663] ? __warn+0x7c/0x110[ 682.611050] ? notifier_chain_register+0x3e/0x90[ 682.611556] ? report_bug+0x148/0x170[ 682.611977] ? handle_bug+0x36/0x70[ 682.612384] ? exc_invalid_op+0x13/0x60[ 682.612817] ? asm_exc_invalid_op+0x16/0x20[ 682.613284] ? notifier_chain_register+0x3e/0x90[ 682.613789] atomic_notifier_chain_register+0x25/0x40[ 682.614322] mlx5_eswitch_enable_locked+0x1d4/0x3b0 [mlx5_core][ 682.614965] mlx5_eswitch_enable+0xc9/0x100 [mlx5_core][ 682.615551] mlx5_device_enable_sriov+0x25/0x340 [mlx5_core][ 682.616170] mlx5_core_sriov_configure+0x50/0x170 [mlx5_core][ 682.616789] sriov_numvfs_store+0xb0/0x1b0[ 682.617248] kernfs_fop_write_iter+0x117/0x1a0[ 682.617734] vfs_write+0x231/0x3f0[ 682.618138] ksys_write+0x63/0xe0[ 682.618536] do_syscall_64+0x4c/0x100[ 682.618958] entry_SYSCALL_64_after_hwframe+0x4b/0x53
漏洞公开时间：2024-11-06 02:15:16
漏洞创建时间：2024-11-06 02:35:20
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2024-50136

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/1da9cfd6c41c2e6bbe624d0568644e1521c33e12
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/599147722c5778c96292e2fbff4103abbdb45b1f
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/9f2ccb6f3888bec45c00121ee43e4e72423b12c1
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/e58fb7ddbab6635191c26dea1af26b91cce00866
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-50136	https://bugzilla.suse.com/show_bug.cgi?id=1232914
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2024-50136	https://bugzilla.suse.com/show_bug.cgi?id=1232914
suse_bugzilla	https://git.kernel.org/stable/c/1da9cfd6c41c2e6bbe624d0568644e1521c33e12	https://bugzilla.suse.com/show_bug.cgi?id=1232914
suse_bugzilla	https://git.kernel.org/stable/c/599147722c5778c96292e2fbff4103abbdb45b1f	https://bugzilla.suse.com/show_bug.cgi?id=1232914
suse_bugzilla	https://git.kernel.org/stable/c/9f2ccb6f3888bec45c00121ee43e4e72423b12c1	https://bugzilla.suse.com/show_bug.cgi?id=1232914
suse_bugzilla	https://git.kernel.org/stable/c/e58fb7ddbab6635191c26dea1af26b91cce00866	https://bugzilla.suse.com/show_bug.cgi?id=1232914
suse_bugzilla	https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-50136.mbox	https://bugzilla.suse.com/show_bug.cgi?id=1232914
suse_bugzilla	https://bugzilla.redhat.com/show_bug.cgi?id=2323912	https://bugzilla.suse.com/show_bug.cgi?id=1232914
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2024110559-CVE-2024-50136-183b@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2323912
debian		https://security-tracker.debian.org/tracker/CVE-2024-50136
mageia		http://advisories.mageia.org/MGASA-2024-0368.html

漏洞分析指导链接：
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息：

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
		https://git.kernel.org/stable/c/1da9cfd6c41c2e6bbe624d0568644e1521c33e12		nvd
		https://git.kernel.org/stable/c/599147722c5778c96292e2fbff4103abbdb45b1f		nvd
		https://git.kernel.org/stable/c/9f2ccb6f3888bec45c00121ee43e4e72423b12c1		nvd
		https://git.kernel.org/stable/c/e58fb7ddbab6635191c26dea1af26b91cce00866		nvd

二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:net/mlx5: Unregister notifier on eswitch init failureIt otherwise remains registered and a subsequent attempt at eswitchenabling might trigger warnings of the sort:[ 682.589148] ------------[ cut here ]------------[ 682.590204] notifier callback eswitch_vport_event [mlx5_core] already registered[ 682.590256] WARNING: CPU: 13 PID: 2660 at kernel/notifier.c:31 notifier_chain_register+0x3e/0x90[...snipped][ 682.610052] Call Trace:[ 682.610369] [ 682.610663] ? __warn+0x7c/0x110[ 682.611050] ? notifier_chain_register+0x3e/0x90[ 682.611556] ? report_bug+0x148/0x170[ 682.611977] ? handle_bug+0x36/0x70[ 682.612384] ? exc_invalid_op+0x13/0x60[ 682.612817] ? asm_exc_invalid_op+0x16/0x20[ 682.613284] ? notifier_chain_register+0x3e/0x90[ 682.613789] atomic_notifier_chain_register+0x25/0x40[ 682.614322] mlx5_eswitch_enable_locked+0x1d4/0x3b0 [mlx5_core][ 682.614965] mlx5_eswitch_enable+0xc9/0x100 [mlx5_core][ 682.615551] mlx5_device_enable_sriov+0x25/0x340 [mlx5_core][ 682.616170] mlx5_core_sriov_configure+0x50/0x170 [mlx5_core][ 682.616789] sriov_numvfs_store+0xb0/0x1b0[ 682.617248] kernfs_fop_write_iter+0x117/0x1a0[ 682.617734] vfs_write+0x231/0x3f0[ 682.618138] ksys_write+0x63/0xe0[ 682.618536] do_syscall_64+0x4c/0x100[ 682.618958] entry_SYSCALL_64_after_hwframe+0x4b/0x53
openEuler评分：
5.5
Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响)：
1.openEuler-24.03-LTS(6.6.0):受影响
2.openEuler-24.03-LTS-SP1(6.6.0):受影响
3.master(6.6.0):不受影响
4.openEuler-20.03-LTS-SP4(4.19.90):不受影响
5.openEuler-22.03-LTS-SP3(5.10.0):不受影响
6.openEuler-22.03-LTS-SP4(5.10.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
1.master(6.6.0):否
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.6.0):否
6.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-24.03-LTS-SP1(6.6.0):否

原因说明：
1.openEuler-24.03-LTS(6.6.0):正常修复
2.openEuler-24.03-LTS-SP1(6.6.0):正常修复
3.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
4.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
5.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在
6.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在
7.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-1097

Hi openeuler-ci-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Kernel, and any of the maintainers.

@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):

修复是否涉及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):

原因说明：
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):

原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如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-2024-50136

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

net/mlx5: Unregister notifier on eswitch init failure

It otherwise remains registered and a subsequent attempt at eswitch
enabling might trigger warnings of the sort:

[ 682.589148] ------------[ cut here ]------------
[ 682.590204] notifier callback eswitch_vport_event [mlx5_core] already registered
[ 682.590256] WARNING: CPU: 13 PID: 2660 at kernel/notifier.c:31 notifier_chain_register+0x3e/0x90
[...snipped]
[ 682.610052] Call Trace:
[ 682.610369]
[ 682.610663] ? __warn+0x7c/0x110
[ 682.611050] ? notifier_chain_register+0x3e/0x90
[ 682.611556] ? report_bug+0x148/0x170
[ 682.611977] ? handle_bug+0x36/0x70
[ 682.612384] ? exc_invalid_op+0x13/0x60
[ 682.612817] ? asm_exc_invalid_op+0x16/0x20
[ 682.613284] ? notifier_chain_register+0x3e/0x90
[ 682.613789] atomic_notifier_chain_register+0x25/0x40
[ 682.614322] mlx5_eswitch_enable_locked+0x1d4/0x3b0 [mlx5_core]
[ 682.614965] mlx5_eswitch_enable+0xc9/0x100 [mlx5_core]
[ 682.615551] mlx5_device_enable_sriov+0x25/0x340 [mlx5_core]
[ 682.616170] mlx5_core_sriov_configure+0x50/0x170 [mlx5_core]
[ 682.616789] sriov_numvfs_store+0xb0/0x1b0
[ 682.617248] kernfs_fop_write_iter+0x117/0x1a0
[ 682.617734] vfs_write+0x231/0x3f0
[ 682.618138] ksys_write+0x63/0xe0
[ 682.618536] do_syscall_64+0x4c/0x100
[ 682.618958] entry_SYSCALL_64_after_hwframe+0x4b/0x53

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:否

@zhixiuzhou 4.受影响版本排查(受影响/不受影响)=> 没有分析或未按正确格式填写，涉及分支: [openEuler-24.03-LTS-SP1]

CVE-2024-50136

影响性分析说明：
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:否

===========================================================

@gitee-cmd ,@gwei3 ,@zhujianwei001 ,@yanxiaobing2020 ,@liujingang09 ,@luoyukai The CVE score needs to be reviewed (the review instruction /approve or /reject means agreement and rejection).

@guo-mengqi ,请给出NVD评分和openEuler评分不一致的理由

CVE-2024-50136

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

net/mlx5: Unregister notifier on eswitch init failure

It otherwise remains registered and a subsequent attempt at eswitch
enabling might trigger warnings of the sort:

[ 682.589148] ------------[ cut here ]------------
[ 682.590204] notifier callback eswitch_vport_event [mlx5_core] already registered
[ 682.590256] WARNING: CPU: 13 PID: 2660 at kernel/notifier.c:31 notifier_chain_register+0x3e/0x90
[...snipped]
[ 682.610052] Call Trace:
[ 682.610369]
[ 682.610663] ? __warn+0x7c/0x110
[ 682.611050] ? notifier_chain_register+0x3e/0x90
[ 682.611556] ? report_bug+0x148/0x170
[ 682.611977] ? handle_bug+0x36/0x70
[ 682.612384] ? exc_invalid_op+0x13/0x60
[ 682.612817] ? asm_exc_invalid_op+0x16/0x20
[ 682.613284] ? notifier_chain_register+0x3e/0x90
[ 682.613789] atomic_notifier_chain_register+0x25/0x40
[ 682.614322] mlx5_eswitch_enable_locked+0x1d4/0x3b0 [mlx5_core]
[ 682.614965] mlx5_eswitch_enable+0xc9/0x100 [mlx5_core]
[ 682.615551] mlx5_device_enable_sriov+0x25/0x340 [mlx5_core]
[ 682.616170] mlx5_core_sriov_configure+0x50/0x170 [mlx5_core]
[ 682.616789] sriov_numvfs_store+0xb0/0x1b0
[ 682.617248] kernfs_fop_write_iter+0x117/0x1a0
[ 682.617734] vfs_write+0x231/0x3f0
[ 682.618138] ksys_write+0x63/0xe0
[ 682.618536] do_syscall_64+0x4c/0x100
[ 682.618958] entry_SYSCALL_64_after_hwframe+0x4b/0x53

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.master(6.1.0):不受影响
2.openEuler-20.03-LTS-SP4:不受影响
3.openEuler-22.03-LTS-SP3:不受影响
4.openEuler-22.03-LTS-SP4:不受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:受影响

修复是否涉及abi变化(是/否)：
1.master(6.1.0):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS-SP3:否
4.openEuler-22.03-LTS-SP4:否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-24.03-LTS-SP1:否

原因说明：
1.master(23.08.5):不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在
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:net/mlx5: Unregister notifier on eswitch init failureIt otherwise remains registered and a subsequent attempt at eswitchenabling might trigger warnings of the sort:[ 682.589148] ------------[ cut here ]------------[ 682.590204] notifier callback eswitch_vport_event [mlx5_core] already registered[ 682.590256] WARNING: CPU: 13 PID: 2660 at kernel/notifier.c:31 notifier_chain_register+0x3e/0x90[...snipped][ 682.610052] Call Trace:[ 682.610369] [ 682.610663] ? __warn+0x7c/0x110[ 682.611050] ? notifier_chain_register+0x3e/0x90[ 682.611556] ? report_bug+0x148/0x170[ 682.611977] ? handle_bug+0x36/0x70[ 682.612384] ? exc_invalid_op+0x13/0x60[ 682.612817] ? asm_exc_invalid_op+0x16/0x20[ 682.613284] ? notifier_chain_register+0x3e/0x90[ 682.613789] atomic_notifier_chain_register+0x25/0x40[ 682.614322] mlx5_eswitch_enable_locked+0x1d4/0x3b0 [mlx5_core][ 682.614965] mlx5_eswitch_enable+0xc9/0x100 [mlx5_core][ 682.615551] mlx5_device_enable_sriov+0x25/0x340 [mlx5_core][ 682.616170] mlx5_core_sriov_configure+0x50/0x170 [mlx5_core][ 682.616789] sriov_numvfs_store+0xb0/0x1b0[ 682.617248] kernfs_fop_write_iter+0x117/0x1a0[ 682.617734] vfs_write+0x231/0x3f0[ 682.618138] ksys_write+0x63/0xe0[ 682.618536] do_syscall_64+0x4c/0x100[ 682.618958] entry_SYSCALL_64_after_hwframe+0x4b/0x53
已分析	2.openEulerScore	5.5
已分析	3.openEulerVector	AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
已分析	4.受影响版本排查	openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-SP1:受影响,master:不受影响,openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,openEuler-24.03-LTS-Next:不受影响
已分析	5.是否涉及abi变化	master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否
已分析	6.原因说明	openEuler-24.03-LTS:正常修复,openEuler-24.03-LTS-SP1:正常修复,master:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在,openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

CVE-2024-50136

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE-2024-50136

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

net/mlx5: Unregister notifier on eswitch init failure

It otherwise remains registered and a subsequent attempt at eswitch
enabling might trigger warnings of the sort:

[ 682.589148] ------------[ cut here ]------------
[ 682.590204] notifier callback eswitch_vport_event [mlx5_core] already registered
[ 682.590256] WARNING: CPU: 13 PID: 2660 at kernel/notifier.c:31 notifier_chain_register+0x3e/0x90
[...snipped]
[ 682.610052] Call Trace:
[ 682.610369]
[ 682.610663] ? __warn+0x7c/0x110
[ 682.611050] ? notifier_chain_register+0x3e/0x90
[ 682.611556] ? report_bug+0x148/0x170
[ 682.611977] ? handle_bug+0x36/0x70
[ 682.612384] ? exc_invalid_op+0x13/0x60
[ 682.612817] ? asm_exc_invalid_op+0x16/0x20
[ 682.613284] ? notifier_chain_register+0x3e/0x90
[ 682.613789] atomic_notifier_chain_register+0x25/0x40
[ 682.614322] mlx5_eswitch_enable_locked+0x1d4/0x3b0 [mlx5_core]
[ 682.614965] mlx5_eswitch_enable+0xc9/0x100 [mlx5_core]
[ 682.615551] mlx5_device_enable_sriov+0x25/0x340 [mlx5_core]
[ 682.616170] mlx5_core_sriov_configure+0x50/0x170 [mlx5_core]
[ 682.616789] sriov_numvfs_store+0xb0/0x1b0
[ 682.617248] kernfs_fop_write_iter+0x117/0x1a0
[ 682.617734] vfs_write+0x231/0x3f0
[ 682.618138] ksys_write+0x63/0xe0
[ 682.618536] do_syscall_64+0x4c/0x100
[ 682.618958] entry_SYSCALL_64_after_hwframe+0x4b/0x53

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-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-SP3:否
3.master(23.08.5):否
4.openEuler-24.03-LTS:否
5.openEuler-24.03-LTS-Next:否
6.openEuler-22.03-LTS-SP4:否
7.openEuler-24.03-LTS-SP1:否

===========================================================

src-openEuler/kernel

内容风险标识

评论 (11)

src-openEuler/kernel .gitee-modal { width: 500px !important; }

内容风险标识

CVE-2024-50136

评论 (11)

搜索帮助

src-openEuler/kernel