RDMA/core: Fix potential use after free in ib_destroy_cq_user()
Summary
| CVE | CVE-2026-92511 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-09-17 17:17:53 UTC |
|---|
| Updated | 2026-09-17 17:17:53 UTC |
|---|
| 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 08f294a1524bc3211a28091daa6c7513828c7d33 42f7a0c7a94003059540cce448acabfa62ad119d git |
Not specified |
| CNA |
Linux |
Linux |
affected 08f294a1524bc3211a28091daa6c7513828c7d33 253c2ed71a532c70fa0e64317ceb02bb1a50c84c git |
Not specified |
| CNA |
Linux |
Linux |
affected 08f294a1524bc3211a28091daa6c7513828c7d33 b85a148731eceffacb6a030950187d785175607f git |
Not specified |
| CNA |
Linux |
Linux |
affected 08f294a1524bc3211a28091daa6c7513828c7d33 197c262dbf94c0f7ab7ac54b66f892ce9f343232 git |
Not specified |
| CNA |
Linux |
Linux |
affected 08f294a1524bc3211a28091daa6c7513828c7d33 8a72a6aad84b3928dbb5e564bff1f56a7ec222ae git |
Not specified |
| CNA |
Linux |
Linux |
affected 08f294a1524bc3211a28091daa6c7513828c7d33 3481bec4dfc4aee24ffea5a547ee95b70b67d9d5 git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.16 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.16 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.188 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.52 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.6 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/8a72a6aad84b3928dbb5e564bff1f56a7ec222ae |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3481bec4dfc4aee24ffea5a547ee95b70b67d9d5 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/42f7a0c7a94003059540cce448acabfa62ad119d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/197c262dbf94c0f7ab7ac54b66f892ce9f343232 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/b85a148731eceffacb6a030950187d785175607f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/253c2ed71a532c70fa0e64317ceb02bb1a50c84c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.