CVE-2025-21970

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-04-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net/mlx5: Bridge, fix the crash caused by LAG state check

When removing LAG device from bridge, NETDEV_CHANGEUPPER event is triggered. Driver finds the lower devices (PFs) to flush all the offloaded entries. And mlx5_lag_is_shared_fdb is checked, it returns false if one of PF is unloaded. In such case, mlx5_esw_bridge_lag_rep_get() and its caller return NULL, instead of the alive PF, and the flush is skipped.

Besides, the bridge fdb entry's lastuse is updated in mlx5 bridge event handler. But this SWITCHDEV_FDB_ADD_TO_BRIDGE event can be ignored 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 workqueue keeps sending that event, which is then handled by kernel bridge notifier. It causes the following crash when accessing the passed bond netdev which is already destroyed.

To fix this issue, remove such checks. LAG state is already checked in commit 15f8f168952f ("net/mlx5: Bridge, verify LAG state when adding bond to bridge"), driver still need to skip offload if LAG becomes invalid 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: ? __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

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

April 1, 2025

Last Modified

November 3, 2025

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-realtime (5.15.0.1086.90) @ jammy2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1083.89~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.142.152~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1086.89) @ jammy2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1050.54) @ jammy2026-05-30ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1024.24) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.142.137) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1091.89) @ jammy2026-05-30ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1081.81) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1091.100~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1085.75) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-fips (5.15.0.1091.76) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-28.28) @ oracular2026-05-30ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1015.16) @ oracular2026-05-30ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1080.78) @ jammy2026-05-30ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1083.89~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-azure-6.11 (6.11.0-1018.18) @ oracular2026-05-30ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1039.42~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1040.42~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-84.84) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1034.35~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1037.37) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1034.35) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-84.84~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1039.43) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2031.32) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-85.85~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1038.44) @ noble2026-05-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1037.38) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1025.27) @ noble2026-05-30ubuntu
linuxKernel @ 5.15.180osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-28 15:35 UTCEPSS rescore
  2. 2026-07-27 14:12 UTCEPSS rescore
  3. 2026-07-26 14:53 UTCEPSS rescore
  4. 2026-07-25 14:17 UTCEPSS rescore
  5. 2026-07-24 14:17 UTCEPSS rescore
  6. 2026-07-24 10:41 UTCOSV refresh
  7. 2026-07-23 14:17 UTCEPSS rescore
  8. 2026-07-23 02:50 UTCEG score recompute
  9. 2026-07-22 14:07 UTCEPSS rescore
  10. 2026-07-22 14:07 UTCEPSS rescore
  11. 2026-07-21 15:24 UTCEPSS rescore
  12. 2026-07-20 17:07 UTCEPSS rescore
  13. 2026-07-19 14:30 UTCEPSS rescore
  14. 2026-07-19 14:30 UTCEPSS rescore
  15. 2026-07-19 02:28 UTCEPSS rescore
  16. 2026-07-19 02:28 UTCEPSS rescore
  17. 2026-07-18 10:03 UTCEPSS rescore
  18. 2026-07-16 17:02 UTCEPSS rescore
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 01:59 UTCEPSS rescore
  22. 2026-07-13 22:29 UTCEPSS rescore
  23. 2026-07-13 22:29 UTCEPSS rescore
  24. 2026-07-13 06:12 UTCEPSS rescore
  25. 2026-07-13 06:12 UTCEPSS rescore
Show 72 more
  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 08:26 UTCEPSS rescore
  5. 2026-07-09 19:09 UTCEPSS rescore
  6. 2026-07-08 15:14 UTCEPSS rescore
  7. 2026-07-07 13:45 UTCEPSS rescore
  8. 2026-07-07 05:51 UTCOSV refresh
  9. 2026-07-06 16:26 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:30 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-06-30 23:21 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-28 04:55 UTCEPSS rescore
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-24 14:04 UTCEPSS rescore
  25. 2026-06-24 14:04 UTCEPSS rescore
  26. 2026-06-23 21:32 UTCEPSS rescore
  27. 2026-06-23 21:32 UTCEPSS rescore
  28. 2026-06-22 14:25 UTCEPSS rescore
  29. 2026-06-22 14:25 UTCEPSS rescore
  30. 2026-06-21 14:56 UTCEPSS rescore
  31. 2026-06-21 14:56 UTCEPSS rescore
  32. 2026-06-21 01:59 UTCEPSS rescore
  33. 2026-06-21 01:59 UTCEPSS rescore
  34. 2026-06-19 19:25 UTCEPSS rescore
  35. 2026-06-19 19:25 UTCEPSS rescore
  36. 2026-06-18 17:52 UTCEPSS rescore
  37. 2026-06-18 17:52 UTCEPSS rescore
  38. 2026-06-18 17:05 UTCOSV refresh
  39. 2026-06-17 17:52 UTCEPSS rescore
  40. 2026-06-16 17:52 UTCEPSS rescore
  41. 2026-06-16 17:52 UTCEPSS rescore
  42. 2026-06-15 17:48 UTCEPSS rescore
  43. 2026-06-14 23:17 UTCEPSS rescore
  44. 2026-06-13 22:59 UTCEPSS rescore
  45. 2026-06-12 23:11 UTCEPSS rescore
  46. 2026-06-11 13:59 UTCEPSS rescore
  47. 2026-06-10 22:18 UTCEPSS rescore
  48. 2026-06-10 13:22 UTCEPSS rescore
  49. 2026-06-08 14:16 UTCEPSS rescore
  50. 2026-06-08 14:16 UTCEPSS rescore
  51. 2026-06-07 15:24 UTCEPSS rescore
  52. 2026-06-07 15:24 UTCEPSS rescore
  53. 2026-06-06 13:47 UTCEPSS rescore
  54. 2026-06-06 13:47 UTCEPSS rescore
  55. 2026-06-05 22:46 UTCEPSS rescore
  56. 2026-06-05 22:46 UTCEPSS rescore
  57. 2026-06-05 06:10 UTCEPSS rescore
  58. 2026-06-05 06:10 UTCEPSS rescore
  59. 2026-06-04 13:11 UTCEPSS rescore
  60. 2026-06-04 13:11 UTCEPSS rescore
  61. 2026-06-02 20:12 UTCEPSS rescore
  62. 2026-06-02 20:12 UTCEPSS rescore
  63. 2026-06-01 13:51 UTCEPSS rescore
  64. 2026-06-01 13:51 UTCEPSS rescore
  65. 2026-05-31 22:30 UTCEPSS rescore
  66. 2026-05-31 22:30 UTCEPSS rescore
  67. 2026-05-31 00:16 UTCEPSS rescore
  68. 2026-05-31 00:16 UTCEPSS rescore
  69. 2026-05-30 08:22 UTCEG score recompute
  70. 2026-05-30 08:22 UTCVendor advisory
  71. 2026-05-30 08:22 UTCGHSA enrichment
  72. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-21970?
CVE-2025-21970 is a medium vulnerability published on April 1, 2025. In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Bridge, fix the crash caused by LAG state check When removing LAG device from bridge, NETDEV_CHANGEUPPER event is triggered. Driver finds the lower devices (PFs) to flush all the offloaded entries. And mlx5lagissharedfdb…
When was CVE-2025-21970 disclosed?
CVE-2025-21970 was first published in the National Vulnerability Database on April 1, 2025, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-21970 actively exploited?
CVE-2025-21970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.4% of all scored CVEs.
What is the CVSS score of CVE-2025-21970?
CVE-2025-21970 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21970?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-21970, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-21970

Explore →

Is Your Infrastructure Affected by CVE-2025-21970?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.