Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97962 Overview
CVE-2026-97962 is a Linux kernel vulnerability in the net/mlx5e driver affecting the representor vnic devlink health reporter. The reporter is created and destroyed along the representor netdev load and unload path, which is not serialized by the devlink instance lock. Destroying the reporter from this path triggers a devl_assert_locked() warning on driver unbind. The resolution moves the reporter's lifecycle to the eswitch devlink port register and unregister paths, which are already serialized by the devlink instance lock.
Critical Impact
Driver unbind operations on Mellanox mlx5 devices trigger kernel warnings due to improper devlink lock serialization, potentially impacting system stability during network driver lifecycle events.
Affected Products
- Linux kernel net/mlx5e driver (Mellanox mlx5 Ethernet driver)
- Systems using Mellanox ConnectX adapters with eswitch representor functionality
- Kernel builds prior to the fix commits 7f26a5e8, d1fcff9b, and dcaba72c
Discovery Timeline
- 2026-09-25 - CVE-2026-97962 published to NVD
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-97962
Vulnerability Analysis
The vulnerability resides in the mlx5e Ethernet driver's handling of representor virtual NIC (vnic) devlink health reporters. Devlink health reporters require serialization through the devlink instance lock to maintain internal consistency. The representor vnic reporter was created and destroyed as part of the representor netdev load and unload sequence, which does not hold the devlink instance lock.
When a user unbinds the driver through sysfs, the unload path invokes devl_health_reporter_destroy() without the required lock held. The kernel emits a WARNING at net/devlink/core.c:259 via devl_assert_locked+0x54/0x70, taints the kernel with W, and prints a full call trace through mlx5e_vport_rep_unload and mlx5_eswitch_unregister_vport_reps.
The fix relocates the reporter's lifecycle to the eswitch devlink port register and unregister paths, which already execute under the devlink instance lock. The reporter handle is stored on mlx5_devlink_port, and mlx5_vport serves as the reporter private data because the diagnose callback only requires a device handle and vport number.
Root Cause
The root cause is a locking contract violation. The devlink subsystem requires callers of health reporter destruction APIs to hold the devlink instance lock. The representor netdev unload path does not acquire this lock, resulting in an assertion failure when devl_assert_locked() runs during driver unbind.
Attack Vector
Triggering the condition requires local privileged access to perform driver unbind operations through sysfs, such as writing to /sys/bus/pci/drivers/mlx5_core/unbind. The issue surfaces during legitimate administrative lifecycle actions and does not represent a remote attack path. The resulting kernel warning indicates a locking defect rather than a direct memory corruption primitive.
For technical details, review the upstream fix commits referenced in the kernel.org stable tree.
Detection Methods for CVE-2026-97962
Indicators of Compromise
- Kernel log entries containing WARNING: net/devlink/core.c:259 at devl_assert_locked+0x54/0x70 on systems using mlx5 drivers
- Call traces referencing mlx5e_vport_rep_unload and mlx5_eswitch_unregister_vport_reps during driver unbind
- Kernel taint flag W appearing after Mellanox driver module unload events
Detection Strategies
- Monitor dmesg and /var/log/kern.log for the specific devl_assert_locked warning pattern tied to mlx5 call paths
- Audit systems running affected kernel versions with Mellanox ConnectX hardware and mlx5 modules loaded
- Correlate driver unbind events (sysfs writes to /sys/bus/pci/drivers/mlx5_core/unbind) with subsequent kernel warnings
Monitoring Recommendations
- Centralize kernel log collection from hosts running mlx5-based networking to detect the warning signature
- Track kernel version inventory to identify systems still running pre-patch builds of the mlx5e driver
- Alert on unexpected driver unbind operations against production networking hardware
How to Mitigate CVE-2026-97962
Immediate Actions Required
- Apply the upstream kernel patches referenced by commits 7f26a5e8, d1fcff9b, and dcaba72c
- Update to a distribution kernel package that includes the fix for the mlx5e representor vnic reporter
- Restrict administrative access to driver unbind operations on production hosts with Mellanox NICs
Patch Information
The fix is available in the Linux stable tree. Apply the patches from commit 7f26a5e8, commit d1fcff9b, and commit dcaba72c. The patches move the representor vnic reporter lifecycle to the eswitch devlink port register and unregister paths and store the reporter handle on mlx5_devlink_port.
Workarounds
- Avoid unbinding or reloading the mlx5_core driver on affected production systems until patches are applied
- Limit CAP_SYS_ADMIN and root access to minimize unauthorized driver lifecycle operations
- Where possible, schedule mlx5 driver maintenance during planned downtime to reduce exposure to the warning condition
# Verify running kernel version and mlx5 module status
uname -r
lsmod | grep mlx5
# Check for the warning signature in kernel logs
dmesg | grep -E 'devl_assert_locked|mlx5e_vport_rep_unload'
# After patching, confirm the updated kernel is in use before resuming unbind operations
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

