RDMA/core: Fix potential use after free in ib_destroy_srq_user()
Summary
| CVE | CVE-2026-92510 |
|---|
| 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_srq_user()
When accessing a SRQ via the netlink path the only synchronization
mechanism for the said SRQ is rdma_restrack_get().
Currently, rdma_restrack_del() is invoked at the end of
ib_destroy_srq_user(), which is too late, since by that point
vendor-specific resources associated with the SRQ might already be
freed. This can leave a short window where the SRQ 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_srq_user(), ensuring that the SRQ is removed from restrack
before its internal resources are released. This guarantees that no new
users hold references to a SRQ 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 48f8a70e899fa4d9c8f00369f482f0382173ece9 a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9 git |
Not specified |
| CNA |
Linux |
Linux |
affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 d3d0eabe6e39b024deb3e085e2d408d037e967c3 git |
Not specified |
| CNA |
Linux |
Linux |
affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 9c704383529044c02122f85a2a9a42cbf14a07a6 git |
Not specified |
| CNA |
Linux |
Linux |
affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 bedd7dee72588c838f5b67197ea8b387e7beb918 git |
Not specified |
| CNA |
Linux |
Linux |
affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 95c992c869df54a6a7061f5f3fb6400244f2af8f git |
Not specified |
| CNA |
Linux |
Linux |
affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 88244ecc71cc0b3ed200f5ef7ddea6686adfd730 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.13 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.13 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/a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d3d0eabe6e39b024deb3e085e2d408d037e967c3 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/88244ecc71cc0b3ed200f5ef7ddea6686adfd730 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/bedd7dee72588c838f5b67197ea8b387e7beb918 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/95c992c869df54a6a7061f5f3fb6400244f2af8f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9c704383529044c02122f85a2a9a42cbf14a07a6 |
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.