CVE-2025-21970

一、漏洞信息
 漏洞编号：[CVE-2025-21970](https://nvd.nist.gov/vuln/detail/CVE-2025-21970)
 漏洞归属组件：[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:net/mlx5: Bridge, fix the crash caused by LAG state checkWhen removing LAG device from bridge, NETDEV_CHANGEUPPER event istriggered. Driver finds the lower devices (PFs) to flush all theoffloaded entries. And mlx5_lag_is_shared_fdb is checked, it returnsfalse if one of PF is unloaded. In such case,mlx5_esw_bridge_lag_rep_get() and its caller return NULL, instead ofthe alive PF, and the flush is skipped.Besides, the bridge fdb entry s lastuse is updated in mlx5 bridgeevent handler. But this SWITCHDEV_FDB_ADD_TO_BRIDGE event can beignored in this case because the upper interface for bond is deleted,and the entry will never be aged because lastuse is never updated.To make things worse, as the entry is alive, mlx5 bridge workqueuekeeps sending that event, which is then handled by kernel bridgenotifier. It causes the following crash when accessing the passed bondnetdev which is already destroyed.To fix this issue, remove such checks. LAG state is already checked incommit 15f8f168952f ( net/mlx5: Bridge, verify LAG state when addingbond to bridge ), driver still need to skip offload if LAG becomesinvalid state after initialization. Oops: stack segment: 0000 [#1] SMP CPU: 3 UID: 0 PID: 23695 Comm: kworker/u40:3 Tainted: G           OE      6.11.0_mlnx #1 Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Workqueue: mlx5_bridge_wq mlx5_esw_bridge_update_work [mlx5_core] RIP: 0010:br_switchdev_event+0x2c/0x110 [bridge] Code: 44 00 00 48 8b 02 48 f7 00 00 02 00 00 74 69 41 54 55 53 48 83 ec 08 48 8b a8 08 01 00 00 48 85 ed 74 4a 48 83 fe 02 48 89 d3 <4c> 8b 65 00 74 23 76 49 48 83 fe 05 74 7e 48 83 fe 06 75 2f 0f b7 RSP: 0018:ffffc900092cfda0 EFLAGS: 00010297 RAX: ffff888123bfe000 RBX: ffffc900092cfe08 RCX: 00000000ffffffff RDX: ffffc900092cfe08 RSI: 0000000000000001 RDI: ffffffffa0c585f0 RBP: 6669746f6e690a30 R08: 0000000000000000 R09: ffff888123ae92c8 R10: 0000000000000000 R11: fefefefefefefeff R12: ffff888123ae9c60 R13: 0000000000000001 R14: ffffc900092cfe08 R15: 0000000000000000 FS:  0000000000000000(0000) GS:ffff88852c980000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f15914c8734 CR3: 0000000002830005 CR4: 0000000000770ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace:  <TASK>  ? __die_body+0x1a/0x60  ? die+0x38/0x60  ? do_trap+0x10b/0x120  ? do_error_trap+0x64/0xa0  ? exc_stack_segment+0x33/0x50  ? asm_exc_stack_segment+0x22/0x30  ? br_switchdev_event+0x2c/0x110 [bridge]  ? sched_balance_newidle.isra.149+0x248/0x390  notifier_call_chain+0x4b/0xa0  atomic_notifier_call_chain+0x16/0x20  mlx5_esw_bridge_update+0xec/0x170 [mlx5_core]  mlx5_esw_bridge_update_work+0x19/0x40 [mlx5_core]  process_scheduled_works+0x81/0x390  worker_thread+0x106/0x250  ? bh_worker+0x110/0x110  kthread+0xb7/0xe0  ? kthread_park+0x80/0x80  ret_from_fork+0x2d/0x50  ? kthread_park+0x80/0x80  ret_from_fork_asm+0x11/0x20  </TASK>
 漏洞公开时间：2025-04-02 00:15:28
 漏洞创建时间：2025-04-02 01:03:05
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2025-21970
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/4b8eeed4fb105770ce6dc84a2c6ef953c7b71cbb |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/5dd8bf6ab1d6db40f5d09603759fa88caec19e7f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/86ff45f5f61ae1d0d17f0f6d8797b052eacfd8f1 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/bd7e3a42800743a7748c83243e4cafc1b995d4c4 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f7bf259a04271165ae667ad21cfc60c6413f25ca |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f90c4d6572488e2bad38cca00f1c59174a538a1a |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-21970 | https://bugzilla.suse.com/show_bug.cgi?id=1240819 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2025-21970 | https://bugzilla.suse.com/show_bug.cgi?id=1240819 |
| suse_bugzilla | https://git.kernel.org/stable/c/4b8eeed4fb105770ce6dc84a2c6ef953c7b71cbb | https://bugzilla.suse.com/show_bug.cgi?id=1240819 |
| suse_bugzilla | https://git.kernel.org/stable/c/5dd8bf6ab1d6db40f5d09603759fa88caec19e7f | https://bugzilla.suse.com/show_bug.cgi?id=1240819 |
| suse_bugzilla | https://git.kernel.org/stable/c/86ff45f5f61ae1d0d17f0f6d8797b052eacfd8f1 | https://bugzilla.suse.com/show_bug.cgi?id=1240819 |
| suse_bugzilla | https://git.kernel.org/stable/c/bd7e3a42800743a7748c83243e4cafc1b995d4c4 | https://bugzilla.suse.com/show_bug.cgi?id=1240819 |
| suse_bugzilla | https://git.kernel.org/stable/c/f7bf259a04271165ae667ad21cfc60c6413f25ca | https://bugzilla.suse.com/show_bug.cgi?id=1240819 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2356661 | https://bugzilla.suse.com/show_bug.cgi?id=1240819 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2025/CVE-2025-21970.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1240819 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2025040146-CVE-2025-21970-fbac@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2356661 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2025-21970 |
| mageia |  | http://advisories.mageia.org/MGASA-2025-0142.html |
| osv | https://git.kernel.org/stable/c/4b8eeed4fb105770ce6dc84a2c6ef953c7b71cbb | https://osv.dev/vulnerability/CVE-2025-21970 |
| osv | https://git.kernel.org/stable/c/5dd8bf6ab1d6db40f5d09603759fa88caec19e7f | https://osv.dev/vulnerability/CVE-2025-21970 |
| osv | https://git.kernel.org/stable/c/86ff45f5f61ae1d0d17f0f6d8797b052eacfd8f1 | https://osv.dev/vulnerability/CVE-2025-21970 |
| osv | https://git.kernel.org/stable/c/bd7e3a42800743a7748c83243e4cafc1b995d4c4 | https://osv.dev/vulnerability/CVE-2025-21970 |
| osv | https://git.kernel.org/stable/c/f7bf259a04271165ae667ad21cfc60c6413f25ca | https://osv.dev/vulnerability/CVE-2025-21970 |
| osv | https://git.kernel.org/stable/c/f90c4d6572488e2bad38cca00f1c59174a538a1a | https://osv.dev/vulnerability/CVE-2025-21970 |
| osv | https://security-tracker.debian.org/tracker/CVE-2025-21970 | https://osv.dev/vulnerability/CVE-2025-21970 |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  openBrain开源漏洞感知系统
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux_kernel | 6.1.132 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=86ff45f5f61ae1d0d17f0f6d8797b052eacfd8f1Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ff9b7521468bc2909293c1cda66a245a49688f6f | linuxkernelcves |
| linux_kernel | 6.6.84 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bd7e3a42800743a7748c83243e4cafc1b995d4c4Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ff9b7521468bc2909293c1cda66a245a49688f6f | linuxkernelcves |
| linux_kernel | 6.12.20 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f7bf259a04271165ae667ad21cfc60c6413f25caIssue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ff9b7521468bc2909293c1cda66a245a49688f6f | linuxkernelcves |
| linux_kernel | 6.13.8 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5dd8bf6ab1d6db40f5d09603759fa88caec19e7fIssue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ff9b7521468bc2909293c1cda66a245a49688f6f | linuxkernelcves |
| linux_kernel | 6.14 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4b8eeed4fb105770ce6dc84a2c6ef953c7b71cbbPlease | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ff9b7521468bc2909293c1cda66a245a49688f6f | linuxkernelcves |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:net/mlx5: Bridge, fix the crash caused by LAG state checkWhen removing LAG device from bridge, NETDEV_CHANGEUPPER event istriggered. Driver finds the lower devices (PFs) to flush all theoffloaded entries. And mlx5_lag_is_shared_fdb is checked, it returnsfalse if one of PF is unloaded. In such case,mlx5_esw_bridge_lag_rep_get() and its caller return NULL, instead ofthe alive PF, and the flush is skipped.Besides, the bridge fdb entry s lastuse is updated in mlx5 bridgeevent handler. But this SWITCHDEV_FDB_ADD_TO_BRIDGE event can beignored in this case because the upper interface for bond is deleted,and the entry will never be aged because lastuse is never updated.To make things worse, as the entry is alive, mlx5 bridge workqueuekeeps sending that event, which is then handled by kernel bridgenotifier. It causes the following crash when accessing the passed bondnetdev which is already destroyed.To fix this issue, remove such checks. LAG state is already checked incommit 15f8f168952f ( net/mlx5: Bridge, verify LAG state when addingbond to bridge ), driver still need to skip offload if LAG becomesinvalid state after initialization. Oops: stack segment: 0000 [#1] SMP CPU: 3 UID: 0 PID: 23695 Comm: kworker/u40:3 Tainted: G           OE      6.11.0_mlnx #1 Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Workqueue: mlx5_bridge_wq mlx5_esw_bridge_update_work [mlx5_core] RIP: 0010:br_switchdev_event+0x2c/0x110 [bridge] Code: 44 00 00 48 8b 02 48 f7 00 00 02 00 00 74 69 41 54 55 53 48 83 ec 08 48 8b a8 08 01 00 00 48 85 ed 74 4a 48 83 fe 02 48 89 d3 <4c> 8b 65 00 74 23 76 49 48 83 fe 05 74 7e 48 83 fe 06 75 2f 0f b7 RSP: 0018:ffffc900092cfda0 EFLAGS: 00010297 RAX: ffff888123bfe000 RBX: ffffc900092cfe08 RCX: 00000000ffffffff RDX: ffffc900092cfe08 RSI: 0000000000000001 RDI: ffffffffa0c585f0 RBP: 6669746f6e690a30 R08: 0000000000000000 R09: ffff888123ae92c8 R10: 0000000000000000 R11: fefefefefefefeff R12: ffff888123ae9c60 R13: 0000000000000001 R14: ffffc900092cfe08 R15: 0000000000000000 FS:  0000000000000000(0000) GS:ffff88852c980000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f15914c8734 CR3: 0000000002830005 CR4: 0000000000770ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace:  <TASK>  ? __die_body+0x1a/0x60  ? die+0x38/0x60  ? do_trap+0x10b/0x120  ? do_error_trap+0x64/0xa0  ? exc_stack_segment+0x33/0x50  ? asm_exc_stack_segment+0x22/0x30  ? br_switchdev_event+0x2c/0x110 [bridge]  ? sched_balance_newidle.isra.149+0x248/0x390  notifier_call_chain+0x4b/0xa0  atomic_notifier_call_chain+0x16/0x20  mlx5_esw_bridge_update+0xec/0x170 [mlx5_core]  mlx5_esw_bridge_update_work+0x19/0x40 [mlx5_core]  process_scheduled_works+0x81/0x390  worker_thread+0x106/0x250  ? bh_worker+0x110/0x110  kthread+0xb7/0xe0  ? kthread_park+0x80/0x80  ret_from_fork+0x2d/0x50  ? kthread_park+0x80/0x80  ret_from_fork_asm+0x11/0x20  </TASK>
 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.openEuler-24.03-LTS-SP2(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.master(6.6.0):不受影响
8.openEuler-24.03-LTS-Next(6.6.0):不受影响

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

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

src-openEuler/kernel

内容风险标识

评论 (7)

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

内容风险标识

CVE-2025-21970

评论 (7)

搜索帮助

src-openEuler/kernel