cve.bz

CVE-2026-93267 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in uverbs_free_dmah() When accessing a dmah via the netlink path the only synchronization mechanism for the said dmah is rdma_restrack_get(). Currently, rdma_restrack_del() is invoked at the end of uverbs_free_dmah(), which is too late, since by that point vendor-specific resources associated with the dmah might already be freed. This can leave a short window where the dmah remains accessible through restrack, leading to a potential use-after-free. Fix this by moving the rdma_restrack_begin_del() call to the start of uverbs_free_dmah(), ensuring that the dmah is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a dmah that is in the process of destruction. In addition, this change preserves the intended inverted order between create and destroy routines: resources are added to restrack at the end of successful creation, and hence shall be removed from the restrack first thing during the destruction flow, which keeps the lifecycle management consistent and predictable.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-93267 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93267?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93267?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-93267 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.17 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.52
Linux7.27.2.6
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux7.2.6-1DEBIAN-CVE-2026-93267
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-93267
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-93267
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-93267
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-93267
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-93267 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-93267 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-93267 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-93267 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-93267 USN-9020-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 27 moreno fix listedUBUNTU-CVE-2026-93267
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-93267
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-93267 USN-8959-1
12 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise Server for NVIDIA 16.1kernel-nvidia64kb, kernel-source-nvidia6.12.0-160100.6.1SUSE-SU-2026:24691-1
openSUSELeap 16.1kernel-default-base6.12.0-160100.9.1.160100.3.14openSUSE-SU-2026:22309-1
openSUSELeap 16.1kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia6.12.0-160100.6.1openSUSE-SU-2026:22313-1
openSUSELeap 16.1kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160100.9.1openSUSE-SU-2026:22309-1
openSUSETumbleweedkernel-source7.2.9-1.1openSUSE-SU-2026:12074-1
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-93267

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A race condition was found in the Linux kernel RDMA subsystem where a Direct Memory Access Handle (DMAH) undergoing deallocation in uverbs_free_dmah() could have its vendor-specific resources freed before it was removed from RDMA resource tracking (restrack), leaving a short window in which the handle could still be reached through the netlink resource-tracking path. A local attacker with access to RDMA devices who is able to create and destroy DMAH objects while issuing concurrent netlink queries could exploit this race to reference already-freed memory, causing a use-after-free that could crash the kernel (denial of service) or potentially lead to privilege escalation. Red Hat has rated this flaw as Moderate for the affected products. The DMAH object APIs that contain this flaw were introduced in recent RHEL 9 (9.8 and later) and RHEL 10 (10.2 and later) kernels, and the flaw is also present in Red Hat In-Vehicle OS 2 and in OpenShift Container Platform releases shipped with affected RHEL 9-based CoreOS kernels. Earlier RHEL 6, 7, and 8 releases and older RHEL 9 and RHEL 10 update streams do not contain the vulnerable code and are therefore not affected. Red Hat has deferred the fix for the affected streams to a future planned update; because exploitation requires local access to RDMA-capable hardware, the ability to create DMAH objects, and winning a narrow race window, the residual risk while the fix is deferred is primarily local denial of service.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-93267.

References

Check your stackJSON