Answer in brief
CVE-2026-72345 records a Unknown severity vulnerability in net/mlx5: LAG, Fix off-by-one in single-FDB error rollback. 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 | >=ddbb5ddc43ad000a984149db5af1133433938404 <40cc06bf71476932e5d139fa326dcd0372766e16 || >=ddbb5ddc43ad000a984149db5af1133433938404 <0f0e4ae6975c773f7854fc48932a267f6c79088f | 40cc06bf71476932e5d139fa326dcd0372766e16, 0f0e4ae6975c773f7854fc48932a267f6c79088f |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback On failure at index i, the reverse cleanup loop in mlx5_lag_create_single_fdb() starts from i, so the failed index itself is rolled back. That can operate on uninitialized state or double-tear-down a rule the add_one path already self-rolled-back. Start the rollback from i - 1 so only successfully-installed entries are undone.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72345 records a Unknown severity vulnerability in net/mlx5: LAG, Fix off-by-one in single-FDB error rollback. 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 | >=ddbb5ddc43ad000a984149db5af1133433938404 <40cc06bf71476932e5d139fa326dcd0372766e16 || >=ddbb5ddc43ad000a984149db5af1133433938404 <0f0e4ae6975c773f7854fc48932a267f6c79088f | 40cc06bf71476932e5d139fa326dcd0372766e16, 0f0e4ae6975c773f7854fc48932a267f6c79088f |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback On failure at index i, the reverse cleanup loop in mlx5_lag_create_single_fdb() starts from i, so the failed index itself is rolled back. That can operate on uninitialized state or double-tear-down a rule the add_one path already self-rolled-back. Start the rollback from i - 1 so only successfully-installed entries are undone.
Quoted source text, attributed separately from HOL analysis.