Device-unload hang via missed slave error events
Published May 27, 2026 · Updated May 27, 2026
Denial of service in Linux Kernel RDMA/mlx5 allows local users to hang device unload during a firmware reset in LAG mode. The LAG bond device is registered only on the master and misses slave sys_error events, so UMR posts succeed after the slave dies but their completions never arrive. Reaching the hang requires local low-privileged access, mlx5 link aggregation, a firmware reset, and device unload; the resulting wait is indefinite.
Summary
What happened
Denial of service in Linux Kernel RDMA/mlx5 allows local users to hang device unload during a firmware reset in LAG mode. The LAG bond device is registered only on the master and misses slave sys_error events, so UMR posts succeed after the slave dies but their completions never arrive. Reaching the hang requires local low-privileged access, mlx5 link aggregation, a firmware reset, and device unload; the resulting wait is indefinite.
The record
- CVE
- CVE-2026-45973
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=542bd62b7a7f37182c9ef192c2bd25d118c144e4
- Affected versionversion=6.11.11 <6.12
- Affected versionversion=6.12.2 <6.12.75
- Affected versionversion=6.13
- Affected versionversion=6.6.64 <6.7
- Affected versionversion=6b0acf6a94c31efa43fce4edc22413a3390f9c05 <c8fb5c965ac7d0104872a8e4f6451f3bc6328199
- Affected versionversion=921fcf2971a1e8d3b904ba2c2905b96f4ec3d4ad
- Affected versionversion=ede132a5cf559f3ab35a4c28bac4f4a6c20334d8 <613f5d4139b6ba801ccd93f9a28943be60d903bc
- Affected versionversion=ede132a5cf559f3ab35a4c28bac4f4a6c20334d8 <6d838873da9cb97551d42316967cc82bf8f8031b
- Affected versionversion=ede132a5cf559f3ab35a4c28bac4f4a6c20334d8 <ebc2164a4cd4314503f1a0c8e7aaf76d7e5fa211
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo