Answer in brief
CVE-2026-72006 records a Unknown severity vulnerability in net/mlx5: free mlx5_st_idx_data on final dealloc. 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 | >=888a7776f4fb04c19bec70c737c61c2f383c6b1e <262da8b6ea03d01ee7ed01ad309e4c89941f6b14 || >=888a7776f4fb04c19bec70c737c61c2f383c6b1e <6eb4cf2fa8997f62c11e0006dc010a1fd89c5a75 || >=888a7776f4fb04c19bec70c737c61c2f383c6b1e <df6134b527a88b3e65ba6ae5073664af091d5fd2 | 262da8b6ea03d01ee7ed01ad309e4c89941f6b14, 6eb4cf2fa8997f62c11e0006dc010a1fd89c5a75, df6134b527a88b3e65ba6ae5073664af091d5fd2 |
| Linux/Linuxgeneric | 6.17 | 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: free mlx5_st_idx_data on final dealloc Workloads that repeatedly allocate and release mkeys carrying TPH steering-tag hints (e.g. churning RDMA MRs) leak one struct mlx5_st_idx_data per cycle; kmemleak flags it as unreferenced and the kmalloc slab grows over time. When the last reference to an ST table entry is dropped, mlx5_st_dealloc_index() removed the entry from idx_xa but the backing mlx5_st_idx_data allocation was never freed. Free idx_data after the xa_erase() so the lifetime of the bookkeeping struct matches the lifetime of the ST entry it tracks.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72006 records a Unknown severity vulnerability in net/mlx5: free mlx5_st_idx_data on final dealloc. 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 | >=888a7776f4fb04c19bec70c737c61c2f383c6b1e <262da8b6ea03d01ee7ed01ad309e4c89941f6b14 || >=888a7776f4fb04c19bec70c737c61c2f383c6b1e <6eb4cf2fa8997f62c11e0006dc010a1fd89c5a75 || >=888a7776f4fb04c19bec70c737c61c2f383c6b1e <df6134b527a88b3e65ba6ae5073664af091d5fd2 | 262da8b6ea03d01ee7ed01ad309e4c89941f6b14, 6eb4cf2fa8997f62c11e0006dc010a1fd89c5a75, df6134b527a88b3e65ba6ae5073664af091d5fd2 |
| Linux/Linuxgeneric | 6.17 | 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: free mlx5_st_idx_data on final dealloc Workloads that repeatedly allocate and release mkeys carrying TPH steering-tag hints (e.g. churning RDMA MRs) leak one struct mlx5_st_idx_data per cycle; kmemleak flags it as unreferenced and the kmalloc slab grows over time. When the last reference to an ST table entry is dropped, mlx5_st_dealloc_index() removed the entry from idx_xa but the backing mlx5_st_idx_data allocation was never freed. Free idx_data after the xa_erase() so the lifetime of the bookkeeping struct matches the lifetime of the ST entry it tracks.
Quoted source text, attributed separately from HOL analysis.