Vulnerability · Published May 27, 2026 · Assigned by Linux

CVE-2026-45973RDMA/mlx5: Fix UMR hang in LAG error state unload

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 94.8% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix UMR hang in LAG error state unload During firmware reset in LAG mode, a race condition causes the driver to hang indefinitely while waiting for UMR completion during device unload. See [1]. In LAG mode the bond device is only registered on the master, so it never sees sys_error events from the slave. During firmware reset this causes UMR waits to hang forever on unload as the slave is dead but the master hasn't entered error state yet, so UMR posts succeed but completions never arrive. Fix this by adding a sys_error notifier that gets registered before MLX5_IB_STAGE_IB_REG and stays alive until after ib_unregister_device(). This ensures error events reach the bond device throughout teardown. [1] Call Trace: __schedule+0x2bd/0x760 schedule+0x37/0xa0 schedule_preempt_disabled+0xa/0x10 __mutex_lock.isra.6+0x2b5/0x4a0 __mlx5_ib_dereg_mr+0x606/0x870 [mlx5_ib] ? __xa_erase+0x4a/0xa0 ? _cond_resched+0x15/0x30 ? wait_for_completion+0x31/0x100 ib_dereg_mr_user+0x48/0xc0 [ib_core] ? rdmacg_uncharge_hierarchy+0xa0/0x100 destroy_hw_idr_uobject+0x20/0x50 [ib_uverbs] uverbs_destroy_uobject+0x37/0x150 [ib_uverbs] __uverbs_cleanup_ufile+0xda/0x140 [ib_uverbs] uverbs_destroy_ufile_hw+0x3a/0xf0 [ib_uverbs] ib_uverbs_remove_one+0xc3/0x140 [ib_uverbs] remove_client_context+0x8b/0xd0 [ib_core] disable_device+0x8c/0x130 [ib_core] __ib_unregister_device+0x10d/0x180 [ib_core] ib_unregister_device+0x21/0x30 [ib_core] __mlx5_ib_remove+0x1e4/0x1f0 [mlx5_ib] auxiliary_bus_remove+0x1e/0x30 device_release_driver_internal+0x103/0x1f0 bus_remove_device+0xf7/0x170 device_del+0x181/0x410 mlx5_rescan_drivers_locked.part.10+0xa9/0x1d0 [mlx5_core] mlx5_disable_lag+0x253/0x260 [mlx5_core] mlx5_lag_disable_change+0x89/0xc0 [mlx5_core] mlx5_eswitch_disable+0x67/0xa0 [mlx5_core] mlx5_unload+0x15/0xd0 [mlx5_core] mlx5_unload_one+0x71/0xc0 [mlx5_core] mlx5_sync_reset_reload_work+0x83/0x100 [mlx5_core] process_one_work+0x1a7/0x360 worker_thread+0x30/0x390 ? create_worker+0x1a0/0x1a0 kthread+0x116/0x130 ? kthread_flush_work_fn+0x10/0x10 ret_from_fork+0x22/0x40

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.85-1DEBIAN-CVE-2026-45973
Debian:14linux6.18.14-1DEBIAN-CVE-2026-45973
Ubuntu:24.04:LTSlinux6.8.0-134.134UBUNTU-CVE-2026-45973
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-aws6.8.0-1060.63UBUNTU-CVE-2026-45973
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1060.63~22.04.1UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-azure6.8.0-1063.71UBUNTU-CVE-2026-45973
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1062.69UBUNTU-CVE-2026-45973
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-gcp6.8.0-1063.69UBUNTU-CVE-2026-45973
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1063.69~22.04.1UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-gke6.8.0-1058.64UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1045.48UBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-136.136~22.04.1UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-ibm6.8.0-1060.61UBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1060.61~22.04.1UBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-134.134.1UBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-134.134.1~22.04.1UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1058.61UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1058.61~22.04.1UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1058.61.1UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1029.30UBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-oracle6.8.0-1057.58UBUNTU-CVE-2026-45973
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1057.58~22.04.1UBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-raspi6.8.0-1060.64UBUNTU-CVE-2026-45973
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-45973
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-45973
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-134.134~22.04.1UBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-45973
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-45973
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1032.33UBUNTU-CVE-2026-45973

Affected products (as reported)

VendorProductVersions
Linux Linux 921fcf2971a1e8d3b904ba2c2905b96f4ec3d4ad – before 33deba9bf5c34335182342588315f3db7dbc56d36b0acf6a94c31efa43fce4edc22413a3390f9c05 – before c8fb5c965ac7d0104872a8e4f6451f3bc6328199ede132a5cf559f3ab35a4c28bac4f4a6c20334d8 – before 6d838873da9cb97551d42316967cc82bf8f8031bede132a5cf559f3ab35a4c28bac4f4a6c20334d8 – before 613f5d4139b6ba801ccd93f9a28943be60d903bcede132a5cf559f3ab35a4c28bac4f4a6c20334d8 – before ebc2164a4cd4314503f1a0c8e7aaf76d7e5fa21109ef1c03a7ac2b57be8aeb0c7a75d538ded2562a542bd62b7a7f37182c9ef192c2bd25d118c144e46.6.64 – before 6.6.160
Linux Linux 6.13

References