The vulnerability in the Linux kernel's mlx5 driver was due to a missing free operation for mlx5_st_idx_data structures during the deallocation of steering-tag (ST) table entries. Specifically, when the last reference to an ST table entry was removed, the entry was erased from the index but the associated mlx5_st_idx_data allocation was not freed, causing a memory leak. This leak was triggered by workloads that repeatedly allocate and release mkeys carrying TPH steering-tag hints, leading to unreferenced memory flagged by kmemleak and gradual growth of the kmalloc slab. The fix involved freeing the idx_data after the xa_erase() call to align the lifetime of the bookkeeping structure with the ST entry it tracks.

The vulnerability causes a memory leak in the kernel memory allocator, which can lead to increased memory consumption over time on affected systems under specific workloads involving RDMA memory region churn. There is no indication of direct exploitation or privilege escalation, but the leak could degrade system stability or performance if left unpatched.

A fix for this vulnerability has been implemented in the Linux kernel. Users should update to a kernel version that includes this fix. Since no vendor advisory or patch links are provided, users should monitor official Linux kernel release notes or trusted sources for the patch availability and apply it accordingly.