CVE-2026-43468net/mlx5: Fix deadlock between devlink lock and esw->wq
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix deadlock between devlink lock and esw->wq esw->work_queue executes esw_functions_changed_event_handler -> esw_vfs_changed_event_handler and acquires the devlink lock. .eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -> mlx5_devlink_eswitch_mode_set -> mlx5_eswitch_disable_locked -> mlx5_eswitch_event_handler_unregister -> flush_workqueue deadlocks when esw_vfs_changed_event_handler executes. Fix that by no longer flushing the work to avoid the deadlock, and using a generation counter to keep track of work relevance. This avoids an old handler manipulating an esw that has undergone one or more mode changes: - the counter is incremented in mlx5_eswitch_event_handler_unregister. - the counter is read and passed to the ephemeral mlx5_host_work struct. - the work handler takes the devlink lock and bails out if the current generation is different than the one it was scheduled to operate on. - mlx5_eswitch_cleanup does the final draining before destroying the wq. No longer flushing the workqueue has the side effect of maybe no longer cancelling pending vport_change_handler work items, but that's ok since those are disabled elsewhere: - mlx5_eswitch_disable_locked disables the vport eq notifier. - mlx5_esw_vport_disable disarms the HW EQ notification and marks vport->enabled under state_lock to false to prevent pending vport handler from doing anything. - mlx5_eswitch_cleanup destroys the workqueue and makes sure all events are disabled/finished.
- CVSS
- 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- May 11, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from f1bc646c9a06f09aad5d8bacb87103b5573ee45e before 0de867f6e34eae6907b367fd152c55e61cb98608; from f1bc646c9a06f09aad5d8bacb87103b5573ee45e before 957d2a58f7f8ebcbdd0a85935e0d2675134b890d; from f1bc646c9a06f09aad5d8bacb87103b5573ee45e before 3c7313cb41b1b427078440364d2f042c276a1c0b; from f1bc646c9a06f09aad5d8bacb87103b5573ee45e before 4a7838bebc38374f74baaf88bf2cf8d439a92923; from f1bc646c9a06f09aad5d8bacb87103b5573ee45e before 90e7e5d14d0bd25ffd019a3aa39d9f1c05fedbe1; from f1bc646c9a06f09aad5d8bacb87103b5573ee45e before aed763abf0e905b4b8d747d1ba9e172961572f57 | CNA record |
linux linux_kernel linux:linux_kernel | from 6.0 before 6.1.167; from 6.2 before 6.6.130; from 6.7 before 6.12.78; from 6.13 before 6.18.19; from 6.19 before 6.19.9; 7.0; 7.0; 7.0 | NVD |
References
- https://git.kernel.org/stable/c/0de867f6e34eae6907b367fd152c55e61cb98608patch
- https://git.kernel.org/stable/c/957d2a58f7f8ebcbdd0a85935e0d2675134b890dpatch
- https://git.kernel.org/stable/c/3c7313cb41b1b427078440364d2f042c276a1c0bpatch
- https://git.kernel.org/stable/c/4a7838bebc38374f74baaf88bf2cf8d439a92923patch
- https://git.kernel.org/stable/c/90e7e5d14d0bd25ffd019a3aa39d9f1c05fedbe1patch
- https://git.kernel.org/stable/c/aed763abf0e905b4b8d747d1ba9e172961572f57patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.