CVE-2026-43013
Published: Fri, 01 May 2026 15:16
Summary
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 oc
Details
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.
Are YOU affected by CVE-2026-43013?
5-second check on your actual server. Reads /etc/os-release, uname -r, and dpkg-query; matches against the live USN + Debian Security Tracker feeds; tells you whether CVE-2026-43013 (and any other live CVE) applies. Anonymous, no signup.
curl https://mindsparkstack.com/scan.sh | bash
References
- https://git.kernel.org/stable/c/7129632cab3e4d23510b21930aa73b8d97a859f5
- https://git.kernel.org/stable/c/89c65f2fcd8801365b410f40a427cbcd7f4c28e9
- https://git.kernel.org/stable/c/a3db46d5f4df92630a96f7bc77b60e75c2353e06
- https://git.kernel.org/stable/c/bf16bca6653679d8a514d6c1c5a2c67065033f14
- https://git.kernel.org/stable/c/c53cf44588a93000f71817a6bb87a66353c48dee
- https://git.kernel.org/stable/c/cfa774e6c920c81e700327bf10db8cb50d5db456
StackPatch runs this match against YOUR installed packages every hour
Free 1-server / $99 lifetime founder seat (50 only) / $19+/mo monthly. Indie pricing.