CVE-2026-43013 net/mlx5: lag: Check for LAG device before creating debugfs

Medium 5.5 Published Updated

A missing check in the Linux kernel mlx5 LAG driver allows a NULL pointer dereference when accessing debugfs, potentially causing a system crash.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-43013?

CVE-2026-43013 is a medium-severity vulnerability in Linux kernel, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Weakness: CWE-476

Which versions are affected by CVE-2026-43013?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-43013?

Apply the vendor's patch.

Is CVE-2026-43013 being exploited?

There is no known exploitation of CVE-2026-43013 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2026-43013, DEBIAN-CVE-2026-43013, GHSA-w9xj-xj3x-qgjh, ROOT-OS-UBUNTU-2404-CVE-2026-43013, UBUNTU-CVE-2026-43013.

Is CVE-2026-43013 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free