Answer in brief
CVE-2026-43013 records a Unknown severity vulnerability in net/mlx5: lag: Check for LAG device before creating debugfs. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7f46a0b7327ae261f9981888708dbca22c283900 <a3db46d5f4df92630a96f7bc77b60e75c2353e06 || >=7f46a0b7327ae261f9981888708dbca22c283900 <7129632cab3e4d23510b21930aa73b8d97a859f5 || >=7f46a0b7327ae261f9981888708dbca22c283900 <cfa774e6c920c81e700327bf10db8cb50d5db456 || >=7f46a0b7327ae261f9981888708dbca22c283900 <c53cf44588a93000f71817a6bb87a66353c48dee || >=7f46a0b7327ae261f9981888708dbca22c283900 <89c65f2fcd8801365b410f40a427cbcd7f4c28e9 || >=7f46a0b7327ae261f9981888708dbca22c283900 <bf16bca6653679d8a514d6c1c5a2c67065033f14 | a3db46d5f4df92630a96f7bc77b60e75c2353e06, 7129632cab3e4d23510b21930aa73b8d97a859f5, cfa774e6c920c81e700327bf10db8cb50d5db456, c53cf44588a93000f71817a6bb87a66353c48dee, 89c65f2fcd8801365b410f40a427cbcd7f4c28e9, bf16bca6653679d8a514d6c1c5a2c67065033f14 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
May 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 6, 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.
Quoted source text, attributed separately from HOL analysis.