{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "d83edab562a496a42720902a1d2effccd05c37c5"
            },
            {
              "fixed": "8b22722f45a29a7c0900b1d4d0bc5da5492ece10"
            },
            {
              "fixed": "bfc119a40c04bbe3daad826f2160ccbfae6c64ce"
            },
            {
              "fixed": "2696626a0be5877f445fb647c25ef43930c777e6"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.17.0"
            },
            {
              "fixed": "6.18.52"
            }
          ],
          "type": "ECOSYSTEM"
        },
        {
          "events": [
            {
              "introduced": "6.19.0"
            },
            {
              "fixed": "7.2.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93267.json"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Fix potential use after free in uverbs_free_dmah()\n\nWhen accessing a dmah via the netlink path the only synchronization\nmechanism for the said dmah is rdma_restrack_get().\nCurrently, rdma_restrack_del() is invoked at the end of\nuverbs_free_dmah(), which is too late, since by that point\nvendor-specific resources associated with the dmah might already be\nfreed. This can leave a short window where the dmah remains accessible\nthrough restrack, leading to a potential use-after-free.\n\nFix this by moving the rdma_restrack_begin_del() call to the start of\nuverbs_free_dmah(), ensuring that the dmah is removed from restrack\nbefore its internal resources are released. This guarantees that no new\nusers hold references to a dmah that is in the process of destruction.\n\nIn addition, this change preserves the intended inverted order\nbetween create and destroy routines: resources are added to\nrestrack at the end of successful creation, and hence shall be removed\nfrom the restrack first thing during the destruction flow, which keeps\nthe lifecycle management consistent and predictable.",
  "id": "CVE-2026-93267",
  "modified": "2026-09-26T03:31:01.431800359Z",
  "published": "2026-09-24T15:52:06.415Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2696626a0be5877f445fb647c25ef43930c777e6"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8b22722f45a29a7c0900b1d4d0bc5da5492ece10"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/bfc119a40c04bbe3daad826f2160ccbfae6c64ce"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93267.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93267"
    },
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    }
  ],
  "schema_version": "1.9.0",
  "summary": "RDMA/core: Fix potential use after free in uverbs_free_dmah()"
}