{"id":"CVE-2026-93267","title":"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_r…","summary":"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_r…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= d83edab562a496a42720902a1d2effccd05c37c5 < 8b22722f45a29a7c0900b1d4d0bc5da5492ece10","Linux >= d83edab562a496a42720902a1d2effccd05c37c5 < bfc119a40c04bbe3daad826f2160ccbfae6c64ce","Linux >= d83edab562a496a42720902a1d2effccd05c37c5 < 2696626a0be5877f445fb647c25ef43930c777e6","Linux 6.17"],"published":"2026-09-24","updated":"2026-09-24","sourceUpdated":"2026-09-24T16:17:23.570","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-93267","references":[{"url":"https://git.kernel.org/stable/c/2696626a0be5877f445fb647c25ef43930c777e6","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/8b22722f45a29a7c0900b1d4d0bc5da5492ece10","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/bfc119a40c04bbe3daad826f2160ccbfae6c64ce","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-24T16:47:15.837Z","slug":"CVE-2026-93267","body":"## Overview\n\nIn 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}