All reports
Medium

kernel: net/mlx5: lag: Check for LAG device before creating debugfs

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-43013

Probability of exploitation in the next 30 days: 0.12%

FIRST EPSS · 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: lag: Check for LAG device before creating debugfs __mlx5_lag_dev_add_mdev() may return 0 (success) even when an error occurs that is handled gracefully. Consequently, the initialization flow proceeds to call mlx5_ldev_add_debugfs() even when there is no valid LAG context. mlx5_ldev_add_debugfs() blindly created the debugfs directory and attributes. This exposed interfaces (like the members file) that rely on a valid ldev pointer, leading to potential NULL pointer dereferences if accessed when ldev is NULL. Add a check to verify that mlx5_lag_dev(dev) returns a valid pointer before attempting to create the debugfs entries.

A flaw was found in the Linux kernel's net/mlx5 driver. An error in the __mlx5_lag_dev_add_mdev() function can lead to the creation of debugfs entries without a valid LAG (Link Aggregation Group) context. This exposes interfaces that rely on a valid pointer, potentially leading to a NULL pointer dereference if accessed. Such a dereference could result in a system crash, causing a denial of service (DoS).