RDMA/core: Fix potential use after free in ib_dealloc_pd_user()
Summary
| CVE | CVE-2026-92507 |
|---|
| 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_dealloc_pd_user()
When accessing a PD via the netlink path the only synchronization
mechanism for the said PD is rdma_restrack_get().
Currently, rdma_restrack_del() is invoked at the end of
ib_dealloc_pd_user(), which is too late, since by that point
vendor-specific resources associated with the PD might already be
freed. This can leave a short window where the PD 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_dealloc_pd_user(), ensuring that the PD is removed from restrack
before its internal resources are released. This guarantees that no new
users hold references to a PD 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 91a7c58fce065506fd98954d27694e5d83c96638 df0e9efe61ca706a07b1c9bf93fcb9032455efc4 git |
Not specified |
| CNA |
Linux |
Linux |
affected 91a7c58fce065506fd98954d27694e5d83c96638 7647363fa02046da681acc3c827d9f301c06e0e7 git |
Not specified |
| CNA |
Linux |
Linux |
affected 91a7c58fce065506fd98954d27694e5d83c96638 d9c0daf9362aad2aeed1d9c5536d108772a8d31c git |
Not specified |
| CNA |
Linux |
Linux |
affected 91a7c58fce065506fd98954d27694e5d83c96638 66d65f36d39759e9f62dc746dc71d862f20f827f git |
Not specified |
| CNA |
Linux |
Linux |
affected 91a7c58fce065506fd98954d27694e5d83c96638 c06f2856a1d7e75a5ff247fc05224aa2452e7265 git |
Not specified |
| CNA |
Linux |
Linux |
affected 91a7c58fce065506fd98954d27694e5d83c96638 8b90e701342275f414e36e7421c502237df241ad git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.10 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10 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/c06f2856a1d7e75a5ff247fc05224aa2452e7265 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/66d65f36d39759e9f62dc746dc71d862f20f827f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d9c0daf9362aad2aeed1d9c5536d108772a8d31c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7647363fa02046da681acc3c827d9f301c06e0e7 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/df0e9efe61ca706a07b1c9bf93fcb9032455efc4 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8b90e701342275f414e36e7421c502237df241ad |
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.