CVE-2026-72006 Linux CVE debrief

Who should care

Linux kernel users and administrators who manage systems with the affected net/mlx5 component should be aware of this vulnerability and take steps to mitigate it. This includes verifying and applying available Linux kernel updates to address the memory leak issue, monitoring Linux kernel component usage for potential memory leak issues, and implementing compensating controls to detect and prevent potential exploitation. System administrators and security teams responsible for Linux kernel-based systems should review the vulnerability details and assess their exposure to this issue. They should also ensure that their systems are updated with the latest security patches and consider implementing additional monitoring and detection measures to identify potential exploitation attempts. Additionally, developers and maintainers of Linux kernel-based systems should review the vulnerability details and assess their exposure to this issue. They should also ensure that their systems are updated with the latest security patches and consider implementing additional monitoring and detection measures to identify potential exploitation attempts. Linux kernel users should verify and apply available updates to prevent potential memory leak issues. Linux kernel users and administrators should review and apply patches as part of standard change control processes, and consider compensating controls for exposed systems while remediation is scheduled and verified. They should also check relevant monitoring, detection, and logs for exposed assets that need extra review, and track exceptions, retest remediated assets, and close the item only after evidence is documented. Linux kernel users and administrators should also consider implementing asset inventory management to track affected systems and prioritize remediation efforts accordingly. Furthermore, they should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. They should also review compensating controls for exposed systems while remediation is scheduled,

Technical summary

The CVE-2026-72006 vulnerability involves a memory leak in the Linux kernel's net/mlx5 component. The issue arises from the failure to free the mlx5_st_idx_data allocation when the last reference to an ST table entry is dropped. This can lead to a memory leak under certain workloads that repeatedly allocate and release mkeys carrying TPH steering-tag hints. 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.

Defensive priority

Linux kernel users should verify and apply available updates to prevent potential memory leak issues.

Recommended defensive actions

• Verify and apply available Linux kernel updates to address the memory leak issue.
• Monitor Linux kernel component usage for potential memory leak issues.
• Implement compensating controls to detect and prevent potential exploitation.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE-2026-72006 vulnerability involves a memory leak in the Linux kernel's net/mlx5 component. Workloads that repeatedly allocate and release mkeys carrying TPH steering-tag hints can lead to a leak of one struct mlx5_st_idx_data per cycle. This issue arises because mlx5_st_dealloc_index() removes the entry from idx_xa but does not free the backing mlx5_st_idx_data allocation. Users are advised to update to a version where the fix is applied, which frees idx_data after xa_erase() to match the lifetime of the ST entry it tracks.

Official resources