UBUNTU-CVE-2025-21970: High severity ubuntu/linux-hwe-edge vulnerability

Q: Which systems are exposed to this issue?

The affected Ubuntu kernel package families listed are linux-realtime, linux-azure, linux-gcp, linux-gke, linux-gkeop, linux-riscv, linux-aws-fips, and linux-azure-fips. The issue concerns systems using the mlx5 driver with bridge and LAG/bond configuration.

Q: What conditions are needed to trigger the crash?

A LAG device must be removed from a bridge, causing a NETDEV_CHANGEUPPER event while one PF is unloaded. A stale bridge FDB entry can then continue generating events after the bond netdev has been destroyed, leading the kernel bridge notifier to access that destroyed device.

Q: Is this remotely exploitable?

The supplied CVSS vector indicates local attack vector, low attack complexity, low privileges required, and no user interaction. It indicates an availability impact only, with high availability impact and no stated confidentiality or integrity impact.

Q: What is the operational impact?

The described result is a kernel crash caused by access to a destroyed bond netdev. The CVSS information rates availability impact as high.

Published Apr 1, 2025

Updated

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, NETDEVCHANGEUPPER event is triggered. Driver finds the lower devices (PFs) to flush all the offloaded entries. And mlx5lagissharedfdb is checked, it returns false if one of PF is unloaded. In such case, mlx5eswbridgelagrepget() 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 SWITCHDEVFDBADDTOBRIDGE 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.0mlnx #1 Tainted: [O]=OOTMODULE, [E]=UNSIGNEDMODULE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Workqueue: mlx5bridgewq mlx5eswbridgeupdatework [mlx5core] RIP: 0010:brswitchdevevent+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> ? diebody+0x1a/0x60 ? die+0x38/0x60 ? dotrap+0x10b/0x120 ? doerrortrap+0x64/0xa0 ? excstacksegment+0x33/0x50 ? asmexcstacksegment+0x22/0x30 ? brswitchdevevent+0x2c/0x110 [bridge] ? schedbalancenewidle.isra.149+0x248/0x390 notifiercallchain+0x4b/0xa0 atomicnotifiercallchain+0x16/0x20 mlx5eswbridgeupdate+0xec/0x170 [mlx5core] mlx5eswbridgeupdatework+0x19/0x40 [mlx5core] processscheduledworks+0x81/0x390 workerthread+0x106/0x250 ? bhworker+0x110/0x110 kthread+0xb7/0xe0 ? kthreadpark+0x80/0x80 retfromfork+0x2d/0x50 ? kthreadpark+0x80/0x80 retfromforkasm+0x11/0x20 </TASK>

Affected Software

158 affected componentsFixes available

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.15<5.15.0-1086.93~20.04.1

5.15.0-1086.93~20.04.1

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.15<5.15.0-1091.100~20.04.1

5.15.0-1091.100~20.04.1

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.15<5.15.0-1085.94~20.04.1

5.15.0-1085.94~20.04.1

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.15<5.15.0-142.152~20.04.1

5.15.0-142.152~20.04.1

ubuntu/linux-hwe-5.8*

ubuntu/linux-ibm-5.15<5.15.0-1078.81~20.04.1

5.15.0-1078.81~20.04.1

ubuntu/linux-intel-5.13*

ubuntu/linux-intel-iotg-5.15<5.15.0-1083.89~20.04.1

5.15.0-1083.89~20.04.1

ubuntu/linux-lowlatency-hwe-5.15<5.15.0-142.152~20.04.1

5.15.0-142.152~20.04.1

ubuntu/linux-nvidia-tegra-5.15<5.15.0-1039.39~20.04.1

5.15.0-1039.39~20.04.1

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.15<5.15.0-1083.89~20.04.1

5.15.0-1083.89~20.04.1

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.15<5.15.0-1081.85~20.04.1

5.15.0-1081.85~20.04.1

ubuntu/linux-riscv-5.8*

ubuntu/linux<5.15.0-142.152

5.15.0-142.152

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws<5.15.0-1086.93

5.15.0-1086.93

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-aws-6.8<6.8.0-1039.41~22.04.1

6.8.0-1039.41~22.04.1

ubuntu/linux-azure<5.15.0-1091.100

5.15.0-1091.100

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-6.8<6.8.0-1036.42~22.04.1

6.8.0-1036.42~22.04.1

ubuntu/linux-azure-fde<5.15.0-1091.100.1

5.15.0-1091.100.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp<5.15.0-1085.94

5.15.0-1085.94

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gcp-6.8<6.8.0-1040.42~22.04.1

6.8.0-1040.42~22.04.1

ubuntu/linux-gke<5.15.0-1083.89

5.15.0-1083.89

ubuntu/linux-gkeop<5.15.0-1068.76

5.15.0-1068.76

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-hwe-6.8<6.8.0-85.85~22.04.1

6.8.0-85.85~22.04.1

ubuntu/linux-ibm<5.15.0-1078.81

5.15.0-1078.81

ubuntu/linux-ibm-6.8<6.8.0-1037.37~22.04.1

6.8.0-1037.37~22.04.1

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-intel-iotg<5.15.0-1081.87

5.15.0-1081.87

ubuntu/linux-kvm<5.15.0-1082.87

5.15.0-1082.87

ubuntu/linux-lowlatency<5.15.0-142.152

5.15.0-142.152

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-lowlatency-hwe-6.8<6.8.0-84.84.1~22.04.1

6.8.0-84.84.1~22.04.1

ubuntu/linux-nvidia<5.15.0-1080.81

5.15.0-1080.81

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-nvidia-6.8<6.8.0-1039.42~22.04.1

6.8.0-1039.42~22.04.1

ubuntu/linux-nvidia-tegra<5.15.0-1039.39

5.15.0-1039.39

ubuntu/linux-nvidia-tegra-igx<5.15.0-1028.28

5.15.0-1028.28

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle<5.15.0-1083.89

5.15.0-1083.89

ubuntu/linux-oracle-6.5*

ubuntu/linux-oracle-6.8<6.8.0-1037.38~22.04.1

6.8.0-1037.38~22.04.1

ubuntu/linux-raspi<5.15.0-1080.83

5.15.0-1080.83

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-riscv-6.8<6.8.0-84.84~22.04.1

6.8.0-84.84~22.04.1

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-xilinx-zynqmp<5.15.0-1050.54

5.15.0-1050.54

ubuntu/linux-bluefield<5.15.0-1069.71

5.15.0-1069.71

ubuntu/linux-intel-iot-realtime<5.15.0-1079.81

5.15.0-1079.81

ubuntu/linux-realtime<5.15.0-1086.95

5.15.0-1086.95

ubuntu/linux-realtime-6.8<6.8.1-1034.35~22.04.1

6.8.1-1034.35~22.04.1

ubuntu/linux-aws-fips*

ubuntu/linux-azure-fips*

ubuntu/linux-fips*

ubuntu/linux-gcp-fips*

ubuntu/linux-aws-fips<5.15.0-1086.93+fips1

5.15.0-1086.93+fips1

ubuntu/linux-azure-fips<5.15.0-1091.100+fips1

5.15.0-1091.100+fips1

ubuntu/linux-fips<5.15.0-142.152+fips1

5.15.0-142.152+fips1

ubuntu/linux-gcp-fips<5.15.0-1085.94+fips1

5.15.0-1085.94+fips1

ubuntu/linux<6.8.0-84.84

6.8.0-84.84

ubuntu/linux-aws<6.8.0-1039.41

6.8.0-1039.41

ubuntu/linux-azure<6.8.0-1038.44

6.8.0-1038.44

ubuntu/linux-azure-6.11<6.11.0-1018.18~24.04.1

6.11.0-1018.18~24.04.1

ubuntu/linux-azure-nvidia<6.8.0-1025.27

6.8.0-1025.27

ubuntu/linux-gcp<6.8.0-1040.42

6.8.0-1040.42

ubuntu/linux-gcp-6.11<6.11.0-1016.16~24.04.1

6.11.0-1016.16~24.04.1

ubuntu/linux-gke<6.8.0-1036.40

6.8.0-1036.40

ubuntu/linux-gkeop<6.8.0-1023.25

6.8.0-1023.25

ubuntu/linux-hwe-6.11<6.11.0-28.28~24.04.1

6.11.0-28.28~24.04.1

ubuntu/linux-ibm<6.8.0-1037.37

6.8.0-1037.37

ubuntu/linux-intel*

ubuntu/linux-lowlatency<6.8.0-84.84.1

6.8.0-84.84.1

ubuntu/linux-lowlatency-hwe-6.11<6.11.0-1015.16~24.04.2

6.11.0-1015.16~24.04.2

ubuntu/linux-nvidia<6.8.0-1039.42

6.8.0-1039.42

ubuntu/linux-nvidia-6.11<6.11.0-1012.12

6.11.0-1012.12

ubuntu/linux-nvidia-lowlatency<6.8.0-1039.42.1

6.8.0-1039.42.1

ubuntu/linux-nvidia-tegra<6.8.0-1010.10

6.8.0-1010.10

ubuntu/linux-oem-6.11<6.11.0-1024.24

6.11.0-1024.24

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle<6.8.0-1037.38

6.8.0-1037.38

ubuntu/linux-raspi<6.8.0-1039.43

6.8.0-1039.43

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-xilinx<6.8.0-1018.19

6.8.0-1018.19

ubuntu/linux-raspi-realtime<6.8.0-2030.31

6.8.0-2030.31

ubuntu/linux-realtime<6.8.1-1034.35

6.8.1-1034.35

ubuntu/linux-aws-fips<6.8.0-1039.41+fips1

6.8.0-1039.41+fips1

ubuntu/linux-azure-fips<6.8.0-1040.46+fips1

6.8.0-1040.46+fips1

ubuntu/linux-fips<6.8.0-84.84+fips1

6.8.0-84.84+fips1

ubuntu/linux-gcp-fips<6.8.0-1040.42+fips1

6.8.0-1040.42+fips1

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1086.93~20.04.1
Upgrade
Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1091.100~20.04.1
Upgrade
Upgrade ubuntu/linux-gcp-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1085.94~20.04.1
Upgrade
Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-142.152~20.04.1
Upgrade
Upgrade ubuntu/linux-ibm-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1078.81~20.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1083.89~20.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-142.152~20.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1039.39~20.04.1
Upgrade
Upgrade ubuntu/linux-oracle-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1083.89~20.04.1
Upgrade
Upgrade ubuntu/linux-riscv-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1081.85~20.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 5.15.0-142.152
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 5.15.0-1086.93
Upgrade
Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.41~22.04.1
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 5.15.0-1091.100
Upgrade
Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1036.42~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 5.15.0-1091.100.1
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 5.15.0-1085.94
Upgrade
Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1040.42~22.04.1
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 5.15.0-1083.89
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 5.15.0-1068.76
Upgrade
Upgrade ubuntu/linux-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-85.85~22.04.1
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 5.15.0-1078.81
Upgrade
Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1037.37~22.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.
Fixed in 5.15.0-1081.87
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 5.15.0-1082.87
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 5.15.0-142.152
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-84.84.1~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 5.15.0-1080.81
Upgrade
Upgrade ubuntu/linux-nvidia-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.42~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 5.15.0-1039.39
Upgrade
Upgrade ubuntu/linux-nvidia-tegra-igx to a version that resolves this vulnerability.
Fixed in 5.15.0-1028.28
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 5.15.0-1083.89
Upgrade
Upgrade ubuntu/linux-oracle-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1037.38~22.04.1
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 5.15.0-1080.83
Upgrade
Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-84.84~22.04.1
Upgrade
Upgrade ubuntu/linux-xilinx-zynqmp to a version that resolves this vulnerability.
Fixed in 5.15.0-1050.54
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 5.15.0-1069.71
Upgrade
Upgrade ubuntu/linux-intel-iot-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1079.81
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 5.15.0-1086.95
Upgrade
Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.1-1034.35~22.04.1
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1086.93+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1091.100+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-142.152+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 5.15.0-1085.94+fips1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.8.0-84.84
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.41
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.8.0-1038.44
Upgrade
Upgrade ubuntu/linux-azure-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1018.18~24.04.1
Upgrade
Upgrade ubuntu/linux-azure-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1025.27
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.8.0-1040.42
Upgrade
Upgrade ubuntu/linux-gcp-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1016.16~24.04.1
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 6.8.0-1036.40
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 6.8.0-1023.25
Upgrade
Upgrade ubuntu/linux-hwe-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-28.28~24.04.1
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 6.8.0-1037.37
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-84.84.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1015.16~24.04.2
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.42
Upgrade
Upgrade ubuntu/linux-nvidia-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1012.12
Upgrade
Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.42.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 6.8.0-1010.10
Upgrade
Upgrade ubuntu/linux-oem-6.11 to a version that resolves this vulnerability.
Fixed in 6.11.0-1024.24
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.8.0-1037.38
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.43
Upgrade
Upgrade ubuntu/linux-xilinx to a version that resolves this vulnerability.
Fixed in 6.8.0-1018.19
Upgrade
Upgrade ubuntu/linux-raspi-realtime to a version that resolves this vulnerability.
Fixed in 6.8.0-2030.31
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.8.1-1034.35
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.41+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1040.46+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-84.84+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1040.42+fips1

Event History

Apr 1, 2025

CVE Published

via OSV·04:15 PM

Data Sourced

via OSV·04:15 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which systems are exposed to this issue?

The affected Ubuntu kernel package families listed are linux-realtime, linux-azure, linux-gcp, linux-gke, linux-gkeop, linux-riscv, linux-aws-fips, and linux-azure-fips. The issue concerns systems using the mlx5 driver with bridge and LAG/bond configuration.

What conditions are needed to trigger the crash?

A LAG device must be removed from a bridge, causing a NETDEV_CHANGEUPPER event while one PF is unloaded. A stale bridge FDB entry can then continue generating events after the bond netdev has been destroyed, leading the kernel bridge notifier to access that destroyed device.

Is this remotely exploitable?

The supplied CVSS vector indicates local attack vector, low attack complexity, low privileges required, and no user interaction. It indicates an availability impact only, with high availability impact and no stated confidentiality or integrity impact.

What is the operational impact?

The described result is a kernel crash caused by access to a destroyed bond netdev. The CVSS information rates availability impact as high.

UBUNTU-CVE-2025-21970: High severity ubuntu/linux-hwe-edge vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Which systems are exposed to this issue?

What conditions are needed to trigger the crash?

Is this remotely exploitable?

What is the operational impact?

Company

Resources

Contact

Frequently Asked Questions

Which systems are exposed to this issue?

What conditions are needed to trigger the crash?

Is this remotely exploitable?

What is the operational impact?