GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-X8Q3-8M8P-MX7V

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32
VLAI
Details

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.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-72006"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:20:59Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: free mlx5_st_idx_data on final dealloc\n\nWorkloads that repeatedly allocate and release mkeys carrying TPH\nsteering-tag hints (e.g. churning RDMA MRs) leak one\nstruct mlx5_st_idx_data per cycle; kmemleak flags it as unreferenced\nand the kmalloc slab grows over time.\n\nWhen the last reference to an ST table entry is dropped,\nmlx5_st_dealloc_index() removed the entry from idx_xa but the backing\nmlx5_st_idx_data allocation was never freed.\n\nFree idx_data after the xa_erase() so the lifetime of the bookkeeping\nstruct matches the lifetime of the ST entry it tracks.",
  "id": "GHSA-x8q3-8m8p-mx7v",
  "modified": "2026-08-15T06:32:08Z",
  "published": "2026-08-15T06:32:08Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72006"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/262da8b6ea03d01ee7ed01ad309e4c89941f6b14"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6eb4cf2fa8997f62c11e0006dc010a1fd89c5a75"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/df6134b527a88b3e65ba6ae5073664af091d5fd2"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…