CVE-2026-92507

RDMA/core: Fix potential use after free in ib_dealloc_pd_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.2%

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.

Affected

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

5.1091a7c58fce065506fd98954d27694e5d83c96638
Vendor states this is fixed in 66d65f36d39759e9f62dc746dc71d862f20f827f (fixed)
Vendor states this is fixed in 7647363fa02046da681acc3c827d9f301c06e0e7 (fixed)
Vendor states this is fixed in 8b90e701342275f414e36e7421c502237df241ad (fixed)
Vendor states this is fixed in c06f2856a1d7e75a5ff247fc05224aa2452e7265 (fixed)
Vendor states this is fixed in d9c0daf9362aad2aeed1d9c5536d108772a8d31c (fixed)
Vendor states this is fixed in df0e9efe61ca706a07b1c9bf93fcb9032455efc4 (fixed)
Vendor states this is fixed in 5.10 (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