CVE-2026-43013
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.
Does this matter?
Lower severity and a low EPSS score (0.12%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.12% probability · 2th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-476
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/7129632cab3e4d23510b21930aa73b8d97a859f5Patch
- https://git.kernel.org/stable/c/89c65f2fcd8801365b410f40a427cbcd7f4c28e9Patch
- https://git.kernel.org/stable/c/a3db46d5f4df92630a96f7bc77b60e75c2353e06Patch
- https://git.kernel.org/stable/c/bf16bca6653679d8a514d6c1c5a2c67065033f14Patch
- https://git.kernel.org/stable/c/c53cf44588a93000f71817a6bb87a66353c48deePatch
- https://git.kernel.org/stable/c/cfa774e6c920c81e700327bf10db8cb50d5db456Patch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.