CVE-2026-43013
net/mlx5: lag: Check for LAG device before creating debugfs
Reported by linux · Published May 1, 2026
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.
EPSS 0.12% · 2.0th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.18 | Amazon Linux | 1:6.18.25-52.107.amzn2023 |
| kernel6.12-devel | Amazon Linux | 1:6.12.83-113.160.amzn2023 |
| python3-perf6.12 | Amazon Linux | 1:6.12.83-113.160.amzn2023 |
| kernel6.12-modules-extra-common | Amazon Linux | 1:6.12.83-113.160.amzn2023 |
| kernel6.12-headers | Amazon Linux | 1:6.12.83-113.160.amzn2023 |
| kernel-modules-extra-common | Amazon Linux | 1:6.1.168-202.320.amzn2023 |
| kernel | Amazon Linux | 1:6.1.168-202.320.amzn2023 |
| perf | Amazon Linux | 1:6.1.168-202.320.amzn2023 |
| linux_kernel | linux | 6.19.12, 6.18.22, 6.12.81, 6.6.134, 6.1.168 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 7f46a0b7327ae261f9981888708dbca22c283900, 7f46a0b7327ae261f9981888708dbca22c283900, 7f46a0b7327ae261f9981888708dbca22c283900 |
| Linux | Linux | 5.19, 0, 6.1.168 |
| amazon:2023 | kernel6.18 | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | perf | 0 |
| linux | linux_kernel | 5.19, 5.19, 5.19 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | kernel-livepatch-6.1.168-202.320 | 0 |
…and 20 more
Timeline
- May 1, 2026 CVE Published
- May 11, 2026 CVE Updated
- May 18, 2026 EPSS Score (24 in total, the first dated here)
- Jun 2, 2026 Security Advisory (120 in total, the first dated here)
- Jul 28, 2026 Coalition ESS Score
- Aug 11, 2026 Distribution Patch (114 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-43013
vulnetix vdb fixes CVE-2026-43013
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-43013/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart