CVE-2026-92511

RDMA/core: Fix potential use after free in ib_destroy_cq_user()

HIGH
7.8
CVSS Score
Published: September 17, 2026 at 04:10 PM UTC
Updated: October 19, 2026 at 10:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in ib_destroy_cq_user() When accessing a CQ via the netlink path the only synchronization mechanism for the said CQ is rdma_restrack_get(). Currently, rdma_restrack_del() is invoked at the end of ib_destroy_cq_user(), which is too late, since by that point vendor-specific resources associated with the CQ might already be freed. This can leave a short window where the CQ 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 ib_destroy_cq_user(), ensuring that the CQ is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a CQ 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

08f294a1524bc3211a28091daa6c7513828c7d334.168f294a1524bc3211a28091daa6c7513828c7d33
Vendor states this is fixed in 197c262dbf94c0f7ab7ac54b66f892ce9f343232 (fixed)
Vendor states this is fixed in 253c2ed71a532c70fa0e64317ceb02bb1a50c84c (fixed)
Vendor states this is fixed in 3481bec4dfc4aee24ffea5a547ee95b70b67d9d5 (fixed)
Vendor states this is fixed in 42f7a0c7a94003059540cce448acabfa62ad119d (fixed)
Vendor states this is fixed in 8a72a6aad84b3928dbb5e564bff1f56a7ec222ae (fixed)
Vendor states this is fixed in b85a148731eceffacb6a030950187d785175607f (fixed)
Vendor states this is fixed in 4.16 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card