CVE-2026-43013: Linux kernel · net/mlx5: lag: Check for LAG device before creating debugfs
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in cfa774e6c920c81e700327bf10db8cb50d5db456 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:33 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in cfa774e6c920c81e700327bf10db8cb50d5db456, c53cf44588a93000f71817a6bb87a66353c48dee, bf16bca6653679d8a514d6c1c5a2c67065033f14 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available in the Linux kernel source code as indicated by the listed fixed commit versions. Users should update to a kernel version that includes these fixes to mitigate the vulnerability.
Description
A vulnerability in the Linux kernel's mlx5 driver for Link Aggregation Group (LAG) devices allowed debugfs entries to be created without verifying the existence of a valid LAG context. This could lead to NULL pointer dereferences when accessing certain debugfs interfaces. The issue was fixed by adding a check to ensure a valid LAG device pointer before creating debugfs entries.
References
- git.kernel.org/stable/c/a3db46d5f4df92630a96f7bc77b60e75c2353e06 (opens in a new tab)
- git.kernel.org/stable/c/7129632cab3e4d23510b21930aa73b8d97a859f5 (opens in a new tab)
- git.kernel.org/stable/c/cfa774e6c920c81e700327bf10db8cb50d5db456 (opens in a new tab)
- git.kernel.org/stable/c/c53cf44588a93000f71817a6bb87a66353c48dee (opens in a new tab)
- git.kernel.org/stable/c/89c65f2fcd8801365b410f40a427cbcd7f4c28e9 (opens in a new tab)
- git.kernel.org/stable/c/bf16bca6653679d8a514d6c1c5a2c67065033f14 (opens in a new tab)